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.
CVE-2026-56334
Score 4.3 from GitHub Security Advisory published 2026-07-01. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 24(Track)EG Risk 24/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
July 1, 2026
Advisory Details (2)
Auto-updated Jul 4, 2026Build status is not persisted to build_requests (stuck pending, last_error never set) due to missing UPDATE RLS policy for API-key/anon access · Advisory · Cap-go/capgo · GitHub
https://github.com/Cap-go/capgo/security/advisories/GHSA-gc46-h5j6-qp6qCapgo - Missing UPDATE RLS Policy for Build Status Persistence | Advisories | VulnCheck
https://www.vulncheck.com/advisories/capgo-missing-update-rls-policy-for-build-status-persistenceVendor Advisories for CVE-2026-56334(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 66× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-31 00:32 UTCEG score recompute
- 2026-07-31 00:32 UTCGHSA enrichment
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 22:08 UTCGHSA enrichment
- 2026-07-28 18:32 UTCEG score recompute
- 2026-07-28 18:32 UTCGHSA enrichment
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-27 16:05 UTCEG score recompute
- 2026-07-27 16:05 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 13:32 UTCEG score recompute
- 2026-07-26 13:32 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
Show 43 moreShow fewer
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 10:54 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 08:31 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 06:08 UTCGHSA enrichment
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 03:44 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 01:20 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 22:57 UTCGHSA enrichment
- 2026-07-09 20:33 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 18:09 UTCGHSA enrichment
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 15:46 UTCGHSA enrichment
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 13:21 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 10:55 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 08:30 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 06:07 UTCGHSA enrichment
- 2026-07-02 03:43 UTCGHSA enrichment
- 2026-07-02 01:21 UTCNVD updateCVSS v4 → 5.3
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 01:20 UTCEG score recompute
- 2026-07-01 01:20 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-284
Frequently asked(5)
What is CVE-2026-56334?
When was CVE-2026-56334 disclosed?
Is CVE-2026-56334 actively exploited?
What is the CVSS score of CVE-2026-56334?
How do I remediate CVE-2026-56334?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56334
Is Your Infrastructure Affected by CVE-2026-56334?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.