CVE-2026-56334

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-07-01. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.3
EG Score
4.3(high)
EPSS
9.1%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 1, 2026

Advisory Details (2)

Auto-updated Jul 4, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Build 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-qp6q
generic

Capgo - Missing UPDATE RLS Policy for Build Status Persistence | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-missing-update-rls-policy-for-build-status-persistence

Vendor 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 22× in last 7d / 22× 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.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 13:21 UTCEG score recompute
  4. 2026-07-06 13:21 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 10:56 UTCEG score recompute
  8. 2026-07-05 10:55 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 08:30 UTCEG score recompute
  12. 2026-07-04 08:30 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 06:07 UTCEG score recompute
  16. 2026-07-03 06:07 UTCGHSA enrichment
  17. 2026-07-02 03:43 UTCEG score recompute
  18. 2026-07-02 03:43 UTCGHSA enrichment
  19. 2026-07-02 01:21 UTCNVD updateCVSS v4 → 5.3
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 01:20 UTCEG score recompute
  22. 2026-07-01 01:20 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56334?
CVE-2026-56334 is a medium vulnerability published on July 1, 2026. Capgo before 12.128.2 lacks an UPDATE row-level security policy for the buildrequests 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 buildrequests…
When was CVE-2026-56334 disclosed?
CVE-2026-56334 was first published in the National Vulnerability Database on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56334 actively exploited?
CVE-2026-56334 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56334?
CVE-2026-56334 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-56334?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56334, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56334

Explore →

Is Your Infrastructure Affected by CVE-2026-56334?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs