dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-56299

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 an authentication bypass vulnerability in the /build/upload/:jobId/* endpoint that allows unauthenticated attackers to trigger consistent 500 errors. Remote attackers can send OPTIONS requests to bypass authentication middleware and invoke tusProxy logic with invalid credentials, enabling trivial request flooding and denial of service.

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 · moderate confidence

Capgo before version 12.128.2 contains an authentication bypass in the /build/upload/:jobId/* endpoint where OPTIONS requests can bypass authentication middleware, allowing unauthenticated attackers to invoke tusProxy logic with invalid credentials and trigger consistent 500 errors leading to denial of service.

MitigationUpgrade to Capgo 12.128.2 or later to remediate the authentication bypass; additionally implement rate limiting on the affected endpoint to mitigate request flooding.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Check Capgo version
    Locate the Capgo installation and retrieve its version number (e.g., check package.json, version file, or run 'capgo --version' if CLI is available)
    Affected if The installed version is lower than 12.128.2
  2. Identify exposed upload endpoint
    Review server configuration or API routing to confirm the /build/upload/:jobId/* endpoint is exposed and accessible from the network
    Affected if The endpoint is publicly or internally accessible without additional network segmentation
  3. Verify OPTIONS request handling
    Send an OPTIONS request to the /build/upload/:jobId/* endpoint with invalid or missing credentials and observe if the request bypasses authentication
    Affected if OPTIONS requests to this endpoint succeed without valid authentication (no 401/403 error)
  4. Confirm 500 error behavior
    Send multiple OPTIONS requests with invalid credentials and check if the server returns consistent 500 errors
    Affected if The server responds with 500 errors for unauthenticated OPTIONS requests, indicating the vulnerability is present

You are affected if Capgo version is below 12.128.2 and the /build/upload/:jobId/* endpoint is accessible, allowing OPTIONS requests to bypass authentication and trigger 500 errors.

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 12.128.2 or later to remediate the authentication bypass; additionally implement rate limiting on the affected endpoint to mitigate request flooding.

Recommended fix Moderate confidence

Capgo version 12.128.2 or later

  1. 1. Identify the currently installed Capgo version using the package manager or application configuration
  2. 2. Review the Capgo release notes for version 12.128.2 to understand changes and any migration requirements
  3. 3. Update the Capgo package dependency in your project to version 12.128.2 or later using your package manager (e.g., npm install, yarn upgrade, or pip install depending on your setup)
  4. 4. Verify the upgrade was successful by checking the installed version
  5. 5. Test the application functionality, particularly the /build/upload/:jobId/* endpoint, to confirm the authentication bypass is resolved
  6. 6. Monitor application logs for any 500 errors or unusual activity

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56299 — 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-56299 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