CVE-2018-20860: libopenmpt before 0.3.13 allows a crash with malformed MED files.

Q: How do I fix CVE-2018-20860?

libopenmpt: upgrade to 0.3.13; leap: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2018-20860 being exploited?

CVE-2018-20860 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-20860 affect?

CVE-2018-20860 affects libopenmpt, leap. Severity is medium (CVSS 6.5). libopenmpt before 0.3.13 allows a crash with malformed MED files.

Q: How urgent is CVE-2018-20860?

Priority 41/100. No elevated risk signals yet.

This month

MEDIUM 6.5UPGRADEMITIGATE

CVE-2018-20860 is a medium-severity flaw (CVSS 6.5) affecting libopenmpt, leap. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

libopenmpt before 0.3.13 allows a crash with malformed MED files.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.3% (top 29%)
CISA exploited list	No
Weakness	CWE-20
Published	2019-07-30
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: openmpt · opensuse

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-07-30 19:15 UTCPublished CVE record published
2026-06-17 01:53 UTCUpdated Record last modified

openmpt libopenmpt UPGRADE

Affected: < 0.3.13

Fixed in: 0.3.13

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libopenmpt || rpm -q libopenmpt || libopenmpt --version

2. UPGRADE to 0.3.13 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libopenmpt

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libopenmpt

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

opensuse leap MITIGATE

Affected: 15.0 · 15.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 15.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-20860?

libopenmpt: upgrade to 0.3.13; leap: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-20860 being exploited?

CVE-2018-20860 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-20860 affect?

CVE-2018-20860 affects libopenmpt, leap. Severity is medium (CVSS 6.5). libopenmpt before 0.3.13 allows a crash with malformed MED files.

How urgent is CVE-2018-20860?

Priority 41/100. No elevated risk signals yet.

Related CVEs

CVE-2019-17113 CRITICAL 9.8 UPGRADE In libopenmpt before 0.3.19 and 0.4.x before 0.4.9, ModPlug_InstrumentName and ModPlug_SampleName in libopenmp
CVE-2019-14383 MEDIUM 6.5 UPGRADE MITIGATE J2B in libopenmpt before 0.4.2 allows an assertion failure during file parsing with debug STLs.
CVE-2019-14382 MEDIUM 6.5 UPGRADE DSM in libopenmpt before 0.4.2 allows an assertion failure during file parsing with debug STLs.
CVE-2019-14381 HIGH 7.5 UPGRADE libopenmpt before 0.4.3 allows a crash due to a NULL pointer dereference when doing a portamento from an OPL i
CVE-2019-14380 MEDIUM 6.5 UPGRADE MITIGATE libopenmpt before 0.4.5 allows a crash during playback due to an out-of-bounds read in XM and MT2 files.

References

← Back to latest CVEs