# CVE-2026-100614: Capgo before 12.244.1 Cross-Tenant Image Overwrite via Metadata Worker

> Authenticated attackers can modify cross-tenant image metadata by exploiting a confused-deputy vulnerability in the metadata worker.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-gfvg-4qqv-cq4m, GHSA-rcrw-pg2v-j9xg

## What is CVE-2026-100614?

CVE-2026-100614 is a high-severity missing authorization vulnerability in Cap-go capgo.app, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Capgo before 12.244.1 contains a cross-tenant integrity vulnerability in the metadata-cleaning worker that trusts image object keys from mutable database rows without validating ownership. An authenticated attacker can place a victim tenant's image key in a row they control, causing the service-role worker to download and re-upload that object with sanitized metadata. Attackers can silently modify metadata in cross-tenant image objects by supplying known victim keys during authorized row updates, bypassing storage access controls through the confused-deputy metadata worker.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-100614 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100614 is a high-severity missing authorization vulnerability in Cap-go capgo.app, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100614 exists.

Affected product: Cap-go capgo.app. 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-100614/ (Markdown: https://insights.sbomify.com/CVE-2026-100614/index.md)
```

## Sources

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

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