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.
References
Configurations
No configuration.
History
23 Jun 2026, 15:16
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/Cap-go/capgo/security/advisories/GHSA-6c9f-9v99-26ww - |
22 Jun 2026, 22:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-06-22 22:16
Updated : 2026-06-23 15:16
NVD link : CVE-2026-56321
Mitre link : CVE-2026-56321
CVE.ORG link : CVE-2026-56321
JSON object : View
Products Affected
No product.
CWE
CWE-306
Missing Authentication for Critical Function
