VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

mpv: vulnerability history, versions and safety

mpv is a package in the OSS-Fuzz ecosystem. Vulert records 4 vulnerabilities for it across 3 releases, from Aug 2025 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M3 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 14 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mpv vulnerabilities

Vulert verdict on mpv i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 14 May 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 4 vulnerabilities on record across 1 year, 3 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 4 over 1 year · 3 in the last year i
  • Latest disclosure 14 May 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for mpv, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
v0.41.0 M1 Yes Details →
v0.40.0 M1 Yes Details →
v0.39.0 M1 Yes Details →

Newest 3 of 3 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for mpv

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
UNKNOWN READ Vulnerability in mpv Package N/A medium 86e12929aa0bbc61946d3804982acf887786a7cb 02 Aug 2025
Segmentation Fault in MPV Package: yuv2rgb4_X_c Vulnerability N/A unrated d1743b641b5b8a51115a9828124c7a9b527115e3 26 Jan 2026
Use-of-Uninitialized-Value Vulnerability in mpv Package N/A medium d1743b641b5b8a51115a9828124c7a9b527115e3 26 Jan 2026
Stack Buffer Overflow Vulnerability in mpv Package N/A medium 6bdacac99153b5a487d108e11d2f8d7678afd2fd 14 May 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About mpv

Is mpv safe to use?

Vulert records 4 vulnerabilities for mpv in OSS-Fuzz: 0 critical, 0 high, 3 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does mpv have?

4 vulnerabilities are recorded for mpv in the OSS-Fuzz ecosystem: 0 critical, 0 high, 3 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mpv vulnerabilities disclosed?

3 vulnerabilities were recorded for mpv in the last 12 months, and the oldest entry in this database dates to 02 Aug 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of mpv are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor mpv for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mpv version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.