# CVE-2026-56082: Capgo - Unauthenticated Cross-Tenant Billing Log Tampering via public.record_build_time RPC

> Unauthenticated attackers can tamper with cross-tenant billing logs and inflate build times via an exposed RPC function, requiring an upgrade to Capgo.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-42xj-3h9w-26h5, GHSA-4q75-4379-394h

## What is CVE-2026-56082?

CVE-2026-56082 is a high-severity missing authorization vulnerability in Cap-go capgo, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-56082?


## How do I fix CVE-2026-56082?

No fix has been published for CVE-2026-56082 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56082 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56082 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56082 and fix it if it is affected.

What it is: CVE-2026-56082 is a high-severity missing authorization vulnerability in Cap-go capgo, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56082 exists.

Affected product: Cap-go capgo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56082/ (Markdown: https://insights.sbomify.com/CVE-2026-56082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56082
- OSV: https://osv.dev/vulnerability/CVE-2026-56082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56082/
Summaries are generated and may contain mistakes; the official description above is the record.