Unauthenticated billing data poisoning via exposed RPC
Published Jun 24, 2026 · Updated Jun 24, 2026
Authorization bypass in Capgo before 12.128.2 allows remote attackers to alter cross-tenant build-time billing records via an RPC call. The SECURITY DEFINER public.record_build_time function grants anon callers INSERT or UPDATE access to public.build_logs without an authorization check. A public Supabase publishable key is sufficient; forged organization and build identifiers can inflate quota usage, corrupt billing data, and increase storage load.
Summary
What happened
Authorization bypass in Capgo before 12.128.2 allows remote attackers to alter cross-tenant build-time billing records via an RPC call. The SECURITY DEFINER public.record_build_time function grants anon callers INSERT or UPDATE access to public.build_logs without an authorization check. A public Supabase publishable key is sufficient; forged organization and build identifiers can inflate quota usage, corrupt billing data, and increase storage load.
The record
- CVE
- CVE-2026-56245
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- Capgo
- Product
- Capgo
- Classifications
- CWE-285, CWE-862, CWE-269, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 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.
Weakness, pattern, technique
Public exploit references
- Capgo record_build_time anonymous RPC 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