Database exhaustion via attacker-controlled rate-limit keys
Published Jun 22, 2026 · Updated Jun 22, 2026
Rate limit bypass in Capgo before 12.128.2 allows remote attackers to exhaust its database through the channel_self endpoint. The endpoint keys its one-request-per-second throttle to the client-supplied device_id, and each accepted value invokes upsertChannelDevicePg to write channel_devices. No authentication binds that identifier to a device, so rotating values creates unbounded junk rows and can interrupt the backend service.
Summary
What happened
Rate limit bypass in Capgo before 12.128.2 allows remote attackers to exhaust its database through the channel_self endpoint. The endpoint keys its one-request-per-second throttle to the client-supplied device_id, and each accepted value invokes upsertChannelDevicePg to write channel_devices. No authentication binds that identifier to a device, so rotating values creates unbounded junk rows and can interrupt the backend service.
The record
- CVE
- CVE-2026-56324
- Published
- Jun 22, 2026
- Updated
- Jun 22, 2026
- Vendor
- Capgo
- Product
- Capgo
- Classifications
- CWE-770, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 22, 2026CVE publishedPublication date reported by the CVE source.
- Jun 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <12.128.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-77p2-9rcr-5w27 request-rotation proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo