Skip to main content
VulnerabilityPublished Updated

CVE-2026-58447: iv-org Invidious · Insecure Direct Object Reference

Affects iv-org InvidiousSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 13 Nov 2026, 03:49 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 3.16.5
CNA (VulnCheck)CVSS 4.07.1
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
iv-orgInvidiousAffected
  • <=2.20260626.0
Fixed in–
GitHubInvidiouspkg:github/InvidiousOther threatsAffected
  • <=2.20260626.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix for this vulnerability exists in a commit after version 2.20260626.0 (commit 77ad416). Users should upgrade to a version that includes this fix to prevent exploitation. Until patched, restrict authenticated user permissions where possible to limit exposure.

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.

References

Community reviews

Loading reviews…