CVE-2026-56335
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 contains an authorization bypass vulnerability where write-scoped API keys can directly mutate protected channel configuration fields through PostgREST by exploiting a null authentication check in the immutability trigger. Attackers with write API keys can modify sensitive channel attributes such as public, allow_emulator, and security-related flags outside intended application routes.
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 an authorization bypass where write-scoped API keys can mutate protected channel configuration fields (public, allow_emulator, security flags) by exploiting a null authentication check in the PostgreSQL immutability trigger through PostgREST, bypassing the intended application-level authorization controls.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Capgo versionCheck the installed Capgo version by querying the application metadata, package.json, or the running service version endpoint. Common commands: npm list @capgo/cli, docker images, or check /opt/capgo/versionAffected if The installed version is earlier than 12.128.2 (e.g., 12.120.0, 12.100.0, etc.)
-
Confirm PostgREST is enabledVerify that PostgREST is deployed as part of the Capgo stack. Check docker-compose.yml, kubernetes manifests, or running processes for the postgrest serviceAffected if PostgREST is exposed and accessible, enabling the bypass pathway
-
Locate write-scoped API keysReview API key configuration in the Capgo dashboard or database. Query the api_keys table for keys with write permissions (scope containing 'write' or 'upload')Affected if Any write-scoped API keys exist in the system
-
Check channel configuration table triggersConnect to the PostgreSQL database and inspect triggers on the channels table. Run: SELECT trigger_name, action_statement FROM information_schema.triggers WHERE event_object_table = 'channels'; Look for immutability triggers related to public, allow_emulator, or security fieldsAffected if Immutability triggers exist but lack proper authentication validation (the vulnerability condition)
-
Test field mutation via PostgRESTUsing a write-scoped API key, attempt a PATCH request through the PostgREST endpoint to modify protected fields: curl -X PATCH https://<api>/channel_updates -H 'Authorization: Bearer <write-key>' -d '{"public": true, "allow_emulator": true}'Affected if The request succeeds and modifies fields that should be protected (this confirms the vulnerability)
You are affected if running Capgo before 12.128.2 with PostgREST enabled and any write-scoped API keys exist in the environment.
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.
From vendor dataUpgrade to Capgo 12.128.2 or later which addresses the null authentication check in the PostgREST immutability trigger. Additionally, audit all PostgREST triggers and API key permission models to ensure protected fields cannot be modified outside authorized application routes.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-56335 — 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-56335 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