CVE-2026-56334

Capgo - Missing UPDATE RLS Policy for Build Status Persistence

MEDIUM
4.3
CVSS Score
Published: June 30, 2026 at 10:08 PM UTC
Updated: July 2, 2026 at 01:52 AM UTC
1 product affected across 1 vendorCapgo

Using Capgo by Capgo?

Get instant alerts when new vulnerabilities affect Capgo - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.3
Exploit prediction
EPSS 0.3%
SSVC
PoC

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 12.128.2
Vendor states this is fixed in 12.128.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.3MEDIUMVulnCheck
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-284

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card