{"document":{"category":"csaf_vex","csaf_version":"2.0","title":"CVE-2026-56082: Supabase - Unauthenticated Cross-Tenant Billing Log Tampering via public.record_build_time RPC","publisher":{"category":"vendor","name":"HarborGuard Database","namespace":"https://database.harborguard.co"},"tracking":{"id":"CVE-2026-56082","status":"final","version":"1","initial_release_date":"2026-06-19T21:39:21.619Z","current_release_date":"2026-06-19T21:39:21.619Z","revision_history":[{"date":"2026-06-19T21:39:21.619Z","number":"1","summary":"Initial machine-readable export from HarborGuard."}]},"distribution":{"tlp":{"label":"WHITE"},"text":"Public CVE data; freely redistributable."},"notes":[{"category":"description","text":"Capgo (Cap-go/capgo) before 12.128.2 contains an improper access control vulnerability in the SECURITY DEFINER PostgREST RPC function public.record_build_time, which is granted to the anon role and callable with only the public Supabase publishable (sb_publishable_*) anon key. An unauthenticated attacker can insert rows into public.build_logs for arbitrary organizations and, because the function uses ON CONFLICT (build_id, org_id) DO UPDATE, can overwrite existing usage/billing records by reusing the same build_id for a target org. This enables cross-tenant tampering of billing build logs and financial-impact denial of service by inflating billable build time.","title":"CVE description"}],"references":[{"category":"self","summary":"CVE-2026-56082 on HarborGuard Database","url":"https://database.harborguard.co/cve/CVE-2026-56082"},{"category":"external","summary":"CVE Record","url":"https://www.cve.org/CVERecord?id=CVE-2026-56082"},{"category":"external","summary":"GHSA Advisory GHSA-42xj-3h9w-26h5","url":"https://github.com/Cap-go/capgo/security/advisories/GHSA-42xj-3h9w-26h5"},{"category":"external","summary":"VulnCheck Advisory: Supabase - Unauthenticated Cross-Tenant Billing Log Tampering via public.record_build_time RPC","url":"https://www.vulncheck.com/advisories/supabase-unauthenticated-cross-tenant-billing-log-tampering-via-public-record-build-time-rpc"}]},"product_tree":{"branches":[{"category":"vendor","name":"Cap-go","branches":[{"category":"product_name","name":"capgo","branches":[{"category":"product_version_range","name":"<12.128.2","product":{"name":"Cap-go capgo <12.128.2","product_id":"CSAFPID-1","product_identification_helper":{"cpe":"cpe:2.3:a:cap-go:capgo:*:*:*:*:*:*:*:*"}}},{"category":"product_version","name":"12.128.2","product":{"name":"Cap-go capgo 12.128.2","product_id":"CSAFPID-2","product_identification_helper":{"cpe":"cpe:2.3:a:cap-go:capgo:*:*:*:*:*:*:*:*"}}}]}]}]},"vulnerabilities":[{"cve":"CVE-2026-56082","title":"Supabase - Unauthenticated Cross-Tenant Billing Log Tampering via public.record_build_time RPC","notes":[{"category":"description","text":"Capgo (Cap-go/capgo) before 12.128.2 contains an improper access control vulnerability in the SECURITY DEFINER PostgREST RPC function public.record_build_time, which is granted to the anon role and callable with only the public Supabase publishable (sb_publishable_*) anon key. An unauthenticated attacker can insert rows into public.build_logs for arbitrary organizations and, because the function uses ON CONFLICT (build_id, org_id) DO UPDATE, can overwrite existing usage/billing records by reusing the same build_id for a target org. This enables cross-tenant tampering of billing build logs and financial-impact denial of service by inflating billable build time.","title":"CVE description"}],"product_status":{"known_affected":["CSAFPID-1"],"fixed":["CSAFPID-2"]},"scores":[{"cvss_v4":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","baseScore":8.7,"baseSeverity":"HIGH"},"products":["CSAFPID-1"]}],"remediations":[{"category":"vendor_fix","details":"Update to a fixed version: 12.128.2.","product_ids":["CSAFPID-1"]}]}]}