dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-56233

HIGH · 8.3 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Capgo before 12.128.2 contains a path traversal vulnerability in the builder upload proxy. Authenticated users with build permissions can append traversal sequences (e.g., ../) to upload paths. The WHATWG URL parser normalizes these sequences, bypassing upload restrictions and allowing access to internal administrative endpoints via the privileged BUILDER_API_KEY header, resulting in server-side privilege escalation.

MitigationUpgrade to Capgo version 12.128.2 or later, which contains the fix for the path traversal vulnerability in the builder upload proxy.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Capgo version
    Run `capgo --version` or check the package.json/version file in your Capgo installation directory to determine the exact version number.
    Affected if The installed version is earlier than 12.128.2 (e.g., 12.128.1, 12.127.x, or any version below 12.128.2).
  2. Locate builder upload proxy configuration
    Search for configuration files related to the builder upload proxy (typically in config/builder.*, uploads.*, or similar naming patterns within the Capgo deployment directory). Check if a builder upload proxy endpoint is defined and accessible.
    Affected if The builder upload proxy feature is enabled and exposed in the Capgo configuration.
  3. Verify authentication settings for builder endpoints
    Inspect the Capgo authentication and authorization configuration to determine which user roles have build permissions and whether the BUILDER_API_KEY header is required for internal administrative endpoints.
    Affected if Users with build permissions can access the builder upload proxy and the BUILDER_API_KEY header is used to protect internal endpoints.
  4. Review access logs for path traversal patterns
    Examine Capgo server logs (typically in logs/ or stdout output) for requests containing "../" sequences sent to upload endpoints, especially those targeting internal or administrative paths.
    Affected if Logs show upload requests with traversal sequences (../) accessing paths outside the intended upload directory.

You are affected if your Capgo version is earlier than 12.128.2 AND the builder upload proxy is enabled, allowing authenticated users with build permissions to exploit path traversal and escalate privileges via the BUILDER_API_KEY header.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Capgo version 12.128.2 or later, which contains the fix for the path traversal vulnerability in the builder upload proxy.

Recommended fix Moderate confidence

Capgo version 12.128.2 or later

  1. 1. Identify the current installed version of Capgo by checking package.json, package-lock.json, or running the CLI version command
  2. 2. If the current version is before 12.128.2, plan for an upgrade to version 12.128.2 or later
  3. 3. Before upgrading in production, test the new version in a staging environment to ensure compatibility
  4. 4. Apply the upgrade using the standard package manager (e.g., npm install @capgo/cli@latest or the specific version)
  5. 5. Verify the upgrade was successful by checking the installed version
  6. 6. Test the builder upload functionality to confirm the path traversal vulnerability is remediated
  7. 7. Monitor for any abnormal behavior or errors after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56233 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56233 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data