# CVE-2026-59704: Cap - Missing Access Control in Video AI Metadata Endpoint

> Authenticated attackers can access private video AI metadata and consume owner credits by supplying arbitrary video IDs to an unprotected endpoint.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/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:** 7 Jul 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-2fr3-3757-j2f7

## What is CVE-2026-59704?

CVE-2026-59704 is a high-severity missing authorization vulnerability in Cap, published on 7 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cap's GET /api/video/ai endpoint fails to validate user ownership or membership before returning private video AI metadata including titles, summaries, and chapters. Authenticated attackers can supply arbitrary video IDs to read sensitive AI-generated content and trigger unauthorized AI generation that consumes the video owner's credits without consent.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-59704 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59704 is a high-severity missing authorization vulnerability in Cap, published on 7 Jul 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-59704 exists.

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

## Sources

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

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