Capgo (backend Supabase edge functions) before 12.128.2 does not apply the global authentication middleware to the GET /private/role_bindings/:org_id endpoint, unlike the POST and DELETE role_bindings routes, so unauthenticated requests reach the handler instead of being rejected at the middleware layer. The handler still performs its own authorization check and returns Unauthorized, so no direct data exposure occurs; the flaw is inconsistent authentication enforcement across HTTP methods that could enable authorization bypass if the handler logic changes.
CVE-2026-56321
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- 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
- 5.3
- EG Score
- 5.3(medium)
- EPSS
- 24.2%
- KEV
- Not listed
Published
June 22, 2026
Last Modified
June 23, 2026
Advisory Details (2)
Auto-updated Jun 23, 2026Missing authentication middleware on GET /private/role_bindings/:org_id (inconsistent auth enforcement) · Advisory · Cap-go/capgo · GitHub
https://github.com/Cap-go/capgo/security/advisories/GHSA-6c9f-9v99-26wwCapgo - Missing Authentication Middleware on GET /private/role_bindings Endpoint | Advisories | VulnCheck
https://www.vulncheck.com/advisories/capgo-missing-authentication-middleware-on-get-private-role-bindings-endpointWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 51× 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-14 04:45 UTCEG score recompute
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 04:32 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 04:19 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 03:59 UTCEG score recompute
- 2026-07-10 03:48 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 03:25 UTCEG score recompute
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 03:14 UTCEG score recompute
- 2026-07-07 03:03 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:49 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:38 UTCEG score recompute
- 2026-07-05 02:31 UTCEPSS rescore
Show 26 moreShow fewer
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 02:26 UTCEG score recompute
- 2026-07-03 01:59 UTCEG score recompute
- 2026-07-02 01:47 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 01:36 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 01:25 UTCEG score recompute
- 2026-06-29 01:14 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 01:02 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-27 00:50 UTCEG score recompute
- 2026-06-26 00:39 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 00:25 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 00:14 UTCEG score recompute
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 00:02 UTCEG score recompute
- 2026-06-23 00:00 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-306
- CVE-2011-10013EG 10.0CRITICAL
- CVE-2014-125124EG 10.0CRITICAL
- CVE-2017-2637EG 10.0EPSS 91%CRITICAL
- CVE-2010-5326EG 10.0 KEVEPSS 97%CRITICAL
- CVE-2018-25134EG 9.8CRITICAL
- CVE-2012-10030EG 9.8CRITICAL
- CVE-2018-21132EG 9.8CRITICAL
- CVE-2014-3449EG 9.8CRITICAL
- CVE-2006-0062EG 9.8CRITICAL
- CVE-2006-0061EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-56321?
When was CVE-2026-56321 disclosed?
Is CVE-2026-56321 actively exploited?
What is the CVSS score of CVE-2026-56321?
How do I remediate CVE-2026-56321?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56321
Is Your Infrastructure Affected by CVE-2026-56321?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.