CVE-2026-56324

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Capgo before 12.128.2 contains a rate limit bypass vulnerability in the channel_self endpoint that allows attackers to circumvent rate limiting by rotating the user-controlled device_id parameter. Attackers can send multiple requests per second by changing device_id values to flood the channel_devices table and cause database exhaustion.

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
18.8%
KEV
Not listed

Published

June 22, 2026

Last Modified

June 24, 2026

Advisory Details (2)

Auto-updated Jun 23, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Capgo - Rate Limit Bypass via User-Controlled device_id Parameter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-rate-limit-bypass-via-user-controlled-device-id-parameter
github Patch Available🟡 PoC Available

Rate limit bypass in channel_self via user-controlled device_id · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-77p2-9rcr-5w27

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 74× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 09:18 UTCEG score recompute
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-12 21:23 UTCEG score recompute
  5. 2026-07-12 08:49 UTCEG score recompute
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 20:55 UTCEG score recompute
  8. 2026-07-11 08:59 UTCEG score recompute
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-10 21:04 UTCEG score recompute
  12. 2026-07-10 09:08 UTCEG score recompute
  13. 2026-07-09 21:11 UTCEG score recompute
  14. 2026-07-09 19:10 UTCEPSS rescore
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-09 09:17 UTCEG score recompute
  17. 2026-07-08 21:23 UTCEG score recompute
  18. 2026-07-08 15:16 UTCEPSS rescore
  19. 2026-07-08 15:16 UTCEPSS rescore
  20. 2026-07-08 09:29 UTCEG score recompute
  21. 2026-07-07 21:36 UTCEG score recompute
  22. 2026-07-07 13:46 UTCEPSS rescore
  23. 2026-07-07 13:46 UTCEPSS rescore
  24. 2026-07-07 09:41 UTCEG score recompute
  25. 2026-07-06 21:46 UTCEG score recompute
Show 49 more
  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 09:50 UTCEG score recompute
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 21:49 UTCEG score recompute
  7. 2026-07-05 09:54 UTCEG score recompute
  8. 2026-07-05 02:31 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 21:59 UTCEG score recompute
  11. 2026-07-04 10:04 UTCEG score recompute
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-03 22:09 UTCEG score recompute
  15. 2026-07-03 10:14 UTCEG score recompute
  16. 2026-07-02 22:19 UTCEG score recompute
  17. 2026-07-02 10:25 UTCEG score recompute
  18. 2026-07-01 22:31 UTCEG score recompute
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-07-01 10:36 UTCEG score recompute
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 22:41 UTCEG score recompute
  23. 2026-06-30 10:47 UTCEG score recompute
  24. 2026-06-29 22:49 UTCEG score recompute
  25. 2026-06-29 14:06 UTCEPSS rescore
  26. 2026-06-29 14:06 UTCEPSS rescore
  27. 2026-06-29 10:55 UTCEG score recompute
  28. 2026-06-28 22:59 UTCEG score recompute
  29. 2026-06-28 14:07 UTCEPSS rescore
  30. 2026-06-28 11:05 UTCEG score recompute
  31. 2026-06-28 04:56 UTCEPSS rescore
  32. 2026-06-28 04:56 UTCEPSS rescore
  33. 2026-06-27 23:10 UTCEG score recompute
  34. 2026-06-27 11:14 UTCEG score recompute
  35. 2026-06-27 03:08 UTCEPSS rescore
  36. 2026-06-26 23:19 UTCEG score recompute
  37. 2026-06-26 11:25 UTCEG score recompute
  38. 2026-06-25 23:31 UTCEG score recompute
  39. 2026-06-25 13:49 UTCEPSS rescore
  40. 2026-06-25 11:36 UTCEG score recompute
  41. 2026-06-24 23:42 UTCEG score recompute
  42. 2026-06-24 14:05 UTCEPSS rescore
  43. 2026-06-24 11:48 UTCEG score recompute
  44. 2026-06-23 23:52 UTCEG score recompute
  45. 2026-06-23 21:33 UTCEPSS rescore
  46. 2026-06-23 21:33 UTCEPSS rescore
  47. 2026-06-23 11:57 UTCEG score recompute
  48. 2026-06-23 00:02 UTCEG score recompute
  49. 2026-06-23 00:00 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56324?
CVE-2026-56324 is a high vulnerability published on June 22, 2026. Capgo before 12.128.2 contains a rate limit bypass vulnerability in the channelself endpoint that allows attackers to circumvent rate limiting by rotating the user-controlled deviceid parameter. Attackers can send multiple requests per second by changing deviceid values to flood the channeldevices…
When was CVE-2026-56324 disclosed?
CVE-2026-56324 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56324 actively exploited?
CVE-2026-56324 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56324?
CVE-2026-56324 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-56324?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56324, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56324

Explore →

Is Your Infrastructure Affected by CVE-2026-56324?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs