dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-56229

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable 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 authorization bypass vulnerability in the /build/status and /build/logs endpoints that allows attackers to access build jobs belonging to different applications by supplying a mismatched app_id and job_id combination. Limited API keys restricted to a single app can retrieve build status and logs from other apps by providing an authorized app_id while using a job_id from an unauthorized app, exposing sensitive build information including logs, metadata, and potentially credentials.

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 has an authorization bypass in the /build/status and /build/logs endpoints. The API fails to validate that a requested job_id actually belongs to the specified app_id, allowing attackers with app-restricted API keys to access build data from other applications by supplying mismatched app_id and job_id pairs. This IDOR-style vulnerability exposes sensitive build logs, metadata, and potentially embedded credentials.

MitigationUpgrade to Capgo 12.128.2 or later, which contains proper authorization validation to ensure job_id belongs to the requested app_id before returning build data.

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
None
Availability
None

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

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 Capgo installation version
    Locate the installed Capgo version number in your deployment (check package.json, docker image tag, or running service version endpoint) and compare it to the affected range: versions before 12.128.2
    Affected if The installed version is earlier than 12.128.2
  2. Confirm API endpoints are exposed
    Check if your Capgo deployment exposes the /build/status and /build/logs API endpoints (typically on port 3000 or behind a reverse proxy at /api/build/*)
    Affected if These API endpoints are accessible and the version is below 12.128.2
  3. Identify API key configuration
    Locate your Capgo API keys in the configuration or environment variables - determine if you are using app-restricted API keys that are scoped to specific applications
    Affected if App-restricted API keys exist and the Capgo version is below 12.128.2
  4. Test authorization boundary
    Using an app-restricted API key scoped to app A, make a request to /build/status or /build/logs with app_id=A but a job_id from a different application (app B), then verify if the API returns build data for that mismatched app_id/job_id combination
    Affected if The API returns build data when the job_id does not belong to the specified app_id, indicating the authorization check is missing

You are affected if Capgo version is earlier than 12.128.2 and your API exposes /build/status or /build/logs endpoints with app-restricted keys that can access data from mismatched app_id/job_id pairs.

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, which contains proper authorization validation to ensure job_id belongs to the requested app_id before returning build data.

Recommended fix Moderate confidence

12.128.2

  1. 1. Identify the current Capgo version in use by checking the application's package.json or running 'capgo --version'
  2. 2. Review the application's dependencies to confirm @capgo/cloudapi or related Capgo packages are present
  3. 3. Upgrade Capgo to version 12.128.2 or later by running 'npm install @capgo/cloudapi@latest' or the equivalent for your package manager
  4. 4. Verify the upgrade was successful by checking the installed version
  5. 5. Test the /build/status and /build/logs endpoints to confirm the authorization bypass is remediated
  6. 6. Ensure API keys with app restrictions now correctly enforce access boundaries

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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