# CVE-2026-56335: Capgo - Channel Configuration Mutation via Write-Scoped API Keys

> Attackers with write-scoped API keys can bypass authorization checks to modify sensitive channel configuration fields in Capgo.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-648m-f972-jcc9, GHSA-ph9c-vwjq-pqhj

## What is CVE-2026-56335?

CVE-2026-56335 is a high-severity missing authorization vulnerability in Capgo, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Capgo 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-56335?


## How do I fix CVE-2026-56335?

No fix has been published for CVE-2026-56335 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56335 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56335 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56335 and fix it if it is affected.

What it is: CVE-2026-56335 is a high-severity missing authorization vulnerability in Capgo, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56335 exists.

Affected product: Capgo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56335/ (Markdown: https://insights.sbomify.com/CVE-2026-56335/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56335
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56335
- OSV: https://osv.dev/vulnerability/CVE-2026-56335

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56335/
Summaries are generated and may contain mistakes; the official description above is the record.