CVE-2026-56233

HIGHPre-NVD 8.38.3—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.3Exploit: 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 path traversal vulnerability in the builder upload proxy that allows authenticated users with build permissions to bypass upload restrictions. Attackers can append traversal sequences to the upload path, which are normalized by the WHATWG URL parser, enabling access to internal administrative endpoints with the privileged BUILDER_API_KEY header and resulting in server-side privilege escalation.

CVSS v3
8.3
EG Score
8.3(high)
EPSS
36.2%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 1, 2026

Advisory Details (2)

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

SSRF and Privilege Escalation in Builder Upload Proxy via Path Traversal · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-qprp-873h-mx6f
generic

Capgo - SSRF and Privilege Escalation via Path Traversal in Builder Upload Proxy | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-ssrf-and-privilege-escalation-via-path-traversal-in-builder-upload-proxy

Vendor Advisories for CVE-2026-56233(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 38× in last 7d / 38× 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-07 02:55 UTCEG score recompute
  2. 2026-07-07 02:55 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 15:44 UTCEG score recompute
  6. 2026-07-06 15:43 UTCGHSA enrichment
  7. 2026-07-06 04:32 UTCEG score recompute
  8. 2026-07-06 04:32 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 17:19 UTCEG score recompute
  12. 2026-07-05 17:19 UTCGHSA enrichment
  13. 2026-07-05 06:08 UTCEG score recompute
  14. 2026-07-05 06:08 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 18:56 UTCEG score recompute
  18. 2026-07-04 18:56 UTCGHSA enrichment
  19. 2026-07-04 07:45 UTCEG score recompute
  20. 2026-07-04 07:45 UTCGHSA enrichment
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-03 20:26 UTCEG score recompute
  24. 2026-07-03 20:26 UTCGHSA enrichment
  25. 2026-07-03 09:15 UTCEG score recompute
Show 13 more
  1. 2026-07-03 09:15 UTCGHSA enrichment
  2. 2026-07-02 22:04 UTCEG score recompute
  3. 2026-07-02 22:04 UTCGHSA enrichment
  4. 2026-07-02 10:53 UTCEG score recompute
  5. 2026-07-02 10:53 UTCGHSA enrichment
  6. 2026-07-01 23:42 UTCEG score recompute
  7. 2026-07-01 23:42 UTCGHSA enrichment
  8. 2026-07-01 17:06 UTCNVD updateCVSS v4 → 8.7
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-07-01 12:31 UTCEG score recompute
  11. 2026-07-01 12:31 UTCGHSA enrichment
  12. 2026-07-01 01:20 UTCEG score recompute
  13. 2026-07-01 01:20 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56233?
CVE-2026-56233 is a high vulnerability published on July 1, 2026. Capgo before 12.128.2 contains a path traversal vulnerability in the builder upload proxy that allows authenticated users with build permissions to bypass upload restrictions. Attackers can append traversal sequences to the upload path, which are normalized by the WHATWG URL parser, enabling access…
When was CVE-2026-56233 disclosed?
CVE-2026-56233 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-56233 actively exploited?
CVE-2026-56233 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 36.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56233?
CVE-2026-56233 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-56233?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56233, 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-56233

Explore →

Is Your Infrastructure Affected by CVE-2026-56233?

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

Start Free Scan →Browse All CVEs