CVE-2026-56250
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 · uneditedCapgo before 12.128.2 allows upload-scoped API keys to modify the mutable app_versions.r2_path field through PostgREST, enabling retargeting to arbitrary R2 bundle objects. Attackers can patch r2_path to point to victim objects, soft-delete the attacker-controlled version, and trigger the on_version_update cleanup function to delete the victim R2 object, causing denial of service and bundle availability disruption.
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 confidenceCapgo before 12.128.2 has a permission boundary confusion vulnerability where upload-scoped API keys can modify the app_versions.r2_path field through PostgREST, allowing attackers to retarget the R2 path to point to arbitrary victim bundle objects. When the attacker-controlled version is soft-deleted, it triggers the on_version_update cleanup function which deletes the now-referenced victim R2 object, causing denial of service.
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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Capgo versionCheck the installed Capgo version by querying the application's version endpoint, checking the package.json or container image tag, or running: capgo --version or checking the /api/health version responseAffected if The installed version is earlier than 12.128.2
-
Verify if upload-scoped API keys existReview your Capgo API key configuration and check if any keys are scoped specifically to upload permissions. Query your key management system or check the PostgREST API key configuration for keys with upload-only scopesAffected if Upload-scoped API keys are active in your environment
-
Inspect PostgREST access policiesExamine the PostgREST policies configured for the app_versions table, specifically focusing on policies that govern the r2_path field modification. Check database roles and RLS policies: SELECT * FROM pg_policies WHERE tablename = 'app_versions';Affected if PostgREST allows modification of the r2_path field by scoped upload keys without strict tenant/application boundary enforcement
-
Check for unauthorized app_versions.r2_path modificationsReview database audit logs or PostgREST query logs for any UPDATE operations on the app_versions table where the r2_path column was modified. Look for changes pointing to unexpected R2 object keysAffected if Any r2_path modifications exist that point to bundle objects outside the legitimate application scope
Your environment is affected if you run Capgo versions before 12.128.2 AND have upload-scoped API keys with the ability to modify app_versions.r2_path through PostgREST.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Capgo to version 12.128.2 or later to remediate this vulnerability. Additionally, audit API key scopes and implement stricter PostgREST policies to prevent cross-tenant or cross-application object reference manipulation.
12.128.2 or later
- Check current Capgo version using `capgo --version` or your deployment's version command
- Review Capgo release notes for version 12.128.2 to understand any migration requirements
- Create a backup of your current Capgo configuration and database
- Upgrade Capgo to version 12.128.2 or later using your package manager or deployment method (e.g., `npm install @capgo/cli@latest` or your respective update mechanism)
- Verify the upgrade completed successfully by checking the new version
- Test that upload-scoped API keys can no longer modify the r2_path field through PostgREST
- Monitor logs to confirm the authorization controls are functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56250 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56250 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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