CVE-2026-56250

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: 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 allows upload-scoped API keys to modify the mutable app_versions.r2_path field through PostgREST, enabling retargeting to arbitrary R2 bundle objects. Attackers can patch r2_path to point to victim objects, soft-delete the attacker-controlled version, and trigger the on_version_update cleanup function to delete the victim R2 object, causing denial of service and bundle availability disruption.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
17.2%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 8, 2026

Advisory Details (2)

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

Capgo - Arbitrary R2 Object Deletion via Mutable r2_path in app_versions | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-arbitrary-r2-object-deletion-via-mutable-r2-path-in-app-versions
github Patch Available🟡 PoC Available

Upload-scoped API key can retarget app_versions.r2_path and trigger deletion of another R2 bundle object · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-pw8p-5jg6-cxj3

Vendor Advisories for CVE-2026-56250(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 40× in last 7d / 44× 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-16 00:31 UTCEG score recompute
  2. 2026-07-16 00:31 UTCGHSA enrichment
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 12:38 UTCEG score recompute
  6. 2026-07-15 12:38 UTCGHSA enrichment
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-15 02:00 UTCEPSS rescore
  9. 2026-07-15 00:44 UTCEG score recompute
  10. 2026-07-15 00:44 UTCGHSA enrichment
  11. 2026-07-14 12:51 UTCEG score recompute
  12. 2026-07-14 12:50 UTCGHSA enrichment
  13. 2026-07-14 00:57 UTCEG score recompute
  14. 2026-07-14 00:57 UTCGHSA enrichment
  15. 2026-07-13 22:31 UTCEPSS rescore
  16. 2026-07-13 13:04 UTCEG score recompute
  17. 2026-07-13 13:04 UTCGHSA enrichment
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-13 06:13 UTCEPSS rescore
  20. 2026-07-13 01:11 UTCEG score recompute
  21. 2026-07-13 01:11 UTCGHSA enrichment
  22. 2026-07-12 13:18 UTCEG score recompute
  23. 2026-07-12 13:17 UTCGHSA enrichment
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-12 01:21 UTCEG score recompute
Show 19 more
  1. 2026-07-12 01:21 UTCGHSA enrichment
  2. 2026-07-11 13:28 UTCEG score recompute
  3. 2026-07-11 13:28 UTCGHSA enrichment
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 01:35 UTCEG score recompute
  7. 2026-07-11 01:35 UTCGHSA enrichment
  8. 2026-07-10 13:40 UTCEG score recompute
  9. 2026-07-10 13:40 UTCGHSA enrichment
  10. 2026-07-10 01:47 UTCEG score recompute
  11. 2026-07-10 01:47 UTCGHSA enrichment
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-09 13:54 UTCEG score recompute
  15. 2026-07-09 13:54 UTCGHSA enrichment
  16. 2026-07-09 02:01 UTCEG score recompute
  17. 2026-07-09 02:00 UTCGHSA enrichment
  18. 2026-07-08 14:07 UTCEG score recompute
  19. 2026-07-08 14:05 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56250?
CVE-2026-56250 is a high vulnerability published on July 8, 2026. Capgo before 12.128.2 allows upload-scoped API keys to modify the mutable appversions.r2path field through PostgREST, enabling retargeting to arbitrary R2 bundle objects. Attackers can patch r2path to point to victim objects, soft-delete the attacker-controlled version, and trigger the…
When was CVE-2026-56250 disclosed?
CVE-2026-56250 was first published in the National Vulnerability Database on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56250 actively exploited?
CVE-2026-56250 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56250?
CVE-2026-56250 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-56250?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56250, 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-56250

Explore →

Is Your Infrastructure Affected by CVE-2026-56250?

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

Start Free Scan →Browse All CVEs