# CVE-2026-58447: Invidious - Cross-User Playlist Video Deletion via Missing Ownership Check

> Authenticated attackers can delete videos from other users' playlists by exploiting missing ownership checks in the video removal endpoint.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/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:** 30 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-85cg-fg77-rrm5

## What is CVE-2026-58447?

CVE-2026-58447 is a high-severity missing authorization vulnerability in iv-org Invidious, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Invidious through 2.20260626.0, fixed in commit 77ad416, contains a broken object level authorization vulnerability that allows authenticated attackers to delete videos from other users' playlists by supplying an arbitrary global video index in the remove_video action of the playlist endpoint. Attackers can obtain per-video index values from the public playlist JSON API and submit them to the playlist video deletion endpoint without ownership validation, permanently removing videos from playlists they do not own.

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

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


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

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

## Is CVE-2026-58447 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58447 is a high-severity missing authorization vulnerability in iv-org Invidious, published on 30 Jun 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-58447 exists.

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

## Sources

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

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