Build status disruption via missing UPDATE policy
Published Jun 30, 2026 · Updated Jun 30, 2026
Improper access control in Capgo before 12.128.2 allows attackers to prevent builder status updates from being persisted. The build_requests table has row-level security enabled but no UPDATE policy for API-key or anonymous roles, so builder writes for status and last_error are rejected. Reachability requires access to the build workflow; affected requests remain pending and lose error details, without reported data disclosure or code execution.
Summary
What happened
Improper access control in Capgo before 12.128.2 allows attackers to prevent builder status updates from being persisted. The build_requests table has row-level security enabled but no UPDATE policy for API-key or anonymous roles, so builder writes for status and last_error are rejected. Reachability requires access to the build workflow; affected requests remain pending and lose error details, without reported data disclosure or code execution.
The record
- CVE
- CVE-2026-56334
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- Capgo
- Product
- Capgo
- Classifications
- CWE-284, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <12.128.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Capgo build-status persistence proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo