VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

mplayer: vulnerability history, versions and safety

mplayer is a package in the Debian ecosystem. Vulert records 69 vulnerabilities for it across 15 releases, from May 2004 to Sep 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
69 vulnerabilities recorded U69
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mplayer vulnerabilities

Vulert verdict on mplayer i

Updated on 23 Oct 2026

Careful: 3 of the 69 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 69 vulnerabilities on record across 18 years, none in the last year.

What to do: Plan around the 3 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 69 over 18 years · 0 in the last year i
  • Latest disclosure 15 Sep 2022 i
  • Highest CVSS 5.5 i
  • With no published fix 3 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 mplayer, 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.

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2004 4
  • 2005 6
  • 2006 2
  • 2007 8
  • 2008 18
  • 2014 6
  • 2017 2
  • 2022 23

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

03 Vulnerabilities

Recorded vulnerabilities for mplayer

The 5 most severe of 69 vulnerabilities recorded for this package

Search all 69 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Out-of-bounds Read Vulnerability in MPlayer 5.5 medium 2:1.4+ds1-1+deb11u1 15 Sep 2022
CVE-2022-38850: Divide By Zero Vulnerability in MPlayer Project mencoder 5.5 medium 2:1.4+ds1-1+deb11u1 15 Sep 2022
Memory Leak Vulnerability in Mplayer 5.5 medium No fix published 15 Sep 2022
Integer Overflow Vulnerability in MPlayer GIF Demuxer Leading to Denial of Service 5.5 medium 2:1.3.0-2 03 Feb 2017
Buffer Overflow Vulnerability in MPlayer: CVE-2022-38864 5.5 medium 2:1.4+ds1-1+deb11u1 15 Sep 2022

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 mplayer

Is mplayer safe to use?

Vulert records 69 vulnerabilities for mplayer in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 69 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does mplayer have?

69 vulnerabilities are recorded for mplayer in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 69 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 mplayer vulnerabilities disclosed?

0 vulnerabilities were recorded for mplayer in the last 12 months, and the oldest entry in this database dates to 04 May 2004. 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 mplayer 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 mplayer for upcoming vulnerabilities?

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