# CVE-2026-56334: Capgo - Missing UPDATE RLS Policy for Build Status Persistence

> Attackers can prevent build status updates from persisting, causing build requests to remain stuck in a pending state due to missing row-level security policies.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/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:** 30 Jun 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-gc46-h5j6-qp6q, GHSA-wx33-g984-7g82

## What is CVE-2026-56334?

CVE-2026-56334 is a medium-severity missing authorization vulnerability in Capgo, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Capgo before 12.128.2 lacks an UPDATE row-level security policy for the build_requests table, preventing API-key and anonymous access from persisting builder status updates. Attackers can exploit this missing policy to cause build status and error details to remain unpersisted, leaving build_requests rows stuck in pending state with null last_error values.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-56334 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56334 is a medium-severity missing authorization vulnerability in Capgo, published on 30 Jun 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-56334 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-56334/ (Markdown: https://insights.sbomify.com/CVE-2026-56334/index.md)
```

## Sources

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

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