# CVE-2026-100626: capgo through 12.128.2 IDOR via PUT /app icon endpoint

> Authenticated users can read cross-tenant private images by supplying arbitrary paths to the app icon endpoint, exposing sensitive user and organization data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/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:** 26 Sep 2026
- **Also known as:** GHSA-84xq-4rv7-p252, GHSA-g675-f5v2-69hx

## What is CVE-2026-100626?

CVE-2026-100626 is a medium-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 through 12.128.2 contains an insecure direct object reference vulnerability in the PUT /app/:appId endpoint that accepts attacker-controlled icon storage paths. Authenticated users can supply arbitrary paths in the private images bucket and obtain service-role-signed URLs valid for 7 days to read cross-tenant objects including user avatars, organization logos, and app icons without authorization.

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

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


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

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

## Is CVE-2026-100626 being exploited?

There is no known exploitation of CVE-2026-100626 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100626 is a medium-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: There is no known exploitation of CVE-2026-100626 in the wild and no public exploit code.

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-100626/ (Markdown: https://insights.sbomify.com/CVE-2026-100626/index.md)
```

## Sources

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

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