Quick answers
- Is CVE-2026-56233 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56233 being exploited in the wild.
- How severe is CVE-2026-56233?
- High severity, with a CVSS score of 8.3, published 30 June 2026.
- Which products and versions are affected?
- Capgo before 12.128.2.
- Is there a fix for CVE-2026-56233?
- A patch was published on 2026-06-30: Fix confirmed in version 12.128.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56233 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-56233?
- Check whether you run Capgo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in the Capgo builder upload proxy (specifically in supabase/functions/_backend/public/build/upload.ts). The application appends user-controlled path segments to the builder upload URL without sanitization. When the request is processed by the WHATWG URL parser in the fetch() API, traversal sequences like '/../' are normalized, allowing an attacker to reach internal administrative endpoints. Because the proxy automatically attaches a privileged BUILDER_API_KEY header to these requests, an authenticated user with build permissions can achieve server-side privilege escalation and SSRF. This allows for the manipulation of build jobs and potential execution of attacker-controlled workloads. The issue is fixed in version 12.128.2.
Affected products
- Capgo Capgo before 12.128.2
Timeline
- 2026-03-17: advisory: GitHub Security Advisory published by maintainers
- 2026-06-30: disclosed: NVD and VulnCheck publication date
- 2026-06-30: patched: Fix confirmed in version 12.128.2