CVE-2026-56320

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: 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 an authorization flaw in POST /private/create_device that accepts a caller-supplied org_id parameter without validating it matches the target app's owner organization. Authenticated attackers can create device records for an application using a foreign organization identifier, bypassing the intended org/app authorization boundary.

CVSS v3
7.1
EG Score
7.1(high)
EPSS
12.7%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 1, 2026

Advisory Details (2)

Auto-updated Jul 3, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Authenticated org/app scope mismatch in /private/create_device allows device creation for an app using a foreign org_id · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-mhrc-qhq8-872f
generic

Capgo - Org/App Scope Mismatch in Device Creation Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-org-app-scope-mismatch-in-device-creation-endpoint

Vendor Advisories for CVE-2026-56320(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 36× in last 7d / 36× 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-06 19:59 UTCEG score recompute
  2. 2026-07-06 19:59 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 08:24 UTCEG score recompute
  6. 2026-07-06 08:24 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 20:48 UTCEG score recompute
  10. 2026-07-05 20:47 UTCGHSA enrichment
  11. 2026-07-05 09:15 UTCEG score recompute
  12. 2026-07-05 09:15 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 21:43 UTCEG score recompute
  16. 2026-07-04 21:43 UTCGHSA enrichment
  17. 2026-07-04 10:11 UTCEG score recompute
  18. 2026-07-04 10:11 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 22:39 UTCEG score recompute
  22. 2026-07-03 22:39 UTCGHSA enrichment
  23. 2026-07-03 11:07 UTCEG score recompute
  24. 2026-07-03 11:07 UTCGHSA enrichment
  25. 2026-07-02 23:33 UTCEG score recompute
Show 11 more
  1. 2026-07-02 23:33 UTCGHSA enrichment
  2. 2026-07-02 12:01 UTCEG score recompute
  3. 2026-07-02 12:01 UTCGHSA enrichment
  4. 2026-07-02 00:28 UTCEG score recompute
  5. 2026-07-02 00:28 UTCGHSA enrichment
  6. 2026-07-01 17:06 UTCNVD updateCVSS v4 → 7.1
  7. 2026-07-01 15:07 UTCEPSS rescore
  8. 2026-07-01 12:52 UTCEG score recompute
  9. 2026-07-01 12:52 UTCGHSA enrichment
  10. 2026-07-01 01:19 UTCEG score recompute
  11. 2026-07-01 01:19 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56320?
CVE-2026-56320 is a high vulnerability published on July 1, 2026. Capgo before 12.128.2 contains an authorization flaw in POST /private/createdevice that accepts a caller-supplied orgid parameter without validating it matches the target app's owner organization. Authenticated attackers can create device records for an application using a foreign organization…
When was CVE-2026-56320 disclosed?
CVE-2026-56320 was first published in the National Vulnerability Database on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56320 actively exploited?
CVE-2026-56320 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56320?
CVE-2026-56320 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-56320?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56320, 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-56320

Explore →

Is Your Infrastructure Affected by CVE-2026-56320?

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

Start Free Scan →Browse All CVEs