VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

mpg123: vulnerability history, versions and safety

mpg123 is a package in the Debian ecosystem. Vulert records 25 vulnerabilities for it across 1 release, from Nov 2003 to Sep 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
25 vulnerabilities recorded U25
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 mpg123 vulnerabilities

Vulert verdict on mpg123 i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 25 vulnerabilities on record across 21 years, none 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 25 over 21 years · 0 in the last year i
  • Latest disclosure 24 Sep 2025 i
  • Highest CVSS 8.3 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 mpg123, 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
1.26.4-1 U2 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2003 2
  • 2005 4
  • 2006 2
  • 2007 2
  • 2009 2
  • 2017 8
  • 2019 2
  • 2024 2
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for mpg123

The 5 most severe of 25 vulnerabilities recorded for this package

Search all 25 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-Based Buffer Over-Read in mpg123: Potential Denial-of-Service Vulnerability 8.3 high 1.25.6-1 09 May 2019
Buffer Overflow Vulnerability in mpg123: CVE-2014-9497 7.5 high 1.18.0-1 29 Aug 2017
Heap-Based Buffer Over-Read in mpg123: Remote Denial of Service Vulnerability 7.5 high 1.25.1-1 29 Jun 2017
Integer Overflow Vulnerability in mpg123: Heap-Based Buffer Overflow Risk 5.5 medium 1.25.6-1 29 Aug 2017
Critical Out-of-Bounds Write Vulnerability in mpg123 Package N/A unrated 1.26.4-1+deb11u1 31 Oct 2024

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 mpg123

Is mpg123 safe to use?

Vulert records 25 vulnerabilities for mpg123 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 25 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 mpg123 have?

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

0 vulnerabilities were recorded for mpg123 in the last 12 months, and the oldest entry in this database dates to 17 Nov 2003. 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 mpg123 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 mpg123 for upcoming vulnerabilities?

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