Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted DSM file to victim
-
ExploitVictim's app parses PATT chunks via ReadDSM()
-
ExecutionnPat exceeds MAX_PATTERNS, out-of-bounds heap write
-
ImpactHeap corruption crashes consuming process
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an application built against libmodplug through 0.8.9.1 to parse an attacker-supplied DSM module file whose header declares more than 240 PATT (pattern) chunks, or whose patt_len field wraps, so that nPat is never bounded by MAX_PATTERNS in CSoundFile::ReadDSM(). The practical trigger is a victim opening or loading the crafted file (CVSS UI:P), which limits exploitation to workflows that process untrusted module files. Impact is bounded to heap corruption and process crash (availability) with only limited integrity effect and no confidentiality disclosure; no authentication is required, but no remote-service exposure exists absent an application that ingests such files. |
| Impact | Signals converge on a medium-severity memory-safety defect, not a top-tier priority. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:H, base 6.9) frames this as a locally-triggered flaw requiring a victim to process a malicious file, with impact dominated by availability (VA:H, i.e. process crash) and only limited integrity (VI:L) and zero confidentiality (VC:N). The CWE-787 out-of-bounds write theoretically raises the specter of code execution, but the description and the vendor advisory characterize the realistic outcome as heap corruption that 'crash[es] the consuming process,' which is consistent with the VA:H / VI:L / VC:N emphasis rather than a full RCE. No EPSS score, KEV listing, or confirmed public exploit is present in the input, so there is no evidence of active or at-scale exploitation; the attached hackmd write-up is a technical analysis whose exploit-code status is not confirmed by the provided data. Note one tension to verify: the 4.0 vector uses AV:L (local) while the attack is actually driven by delivering a crafted file that the target application parses - the 'local' rating reflects that the attacker does not touch the network directly, not that physical/shell access is needed. Overall this reads as a genuine but moderate bug: patch during normal cycles, prioritize only where libmodplug parses untrusted/attacker-supplied module files. |
| Exploit ScenarioDerived | An attacker crafts a malicious DSM module file containing more than 240 PATT chunks (or a wrapping patt_len value) and delivers it to a victim who opens it in a media player or application that uses libmodplug ≤0.8.9.1. When CSoundFile::ReadDSM() parses the file without validating nPat against MAX_PATTERNS, it writes past the allocated pattern array, corrupting the heap and crashing the process. No public exploit has been identified in the provided data, though a technical write-up describing the flaw is referenced. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Processing a malicious DSM module file with libmodplug through 0.8.9.1 triggers a heap-based out-of-bounds write in CSoundFile::ReadDSM(), corrupting heap memory and crashing the consuming process. Exploitation is local in nature: it requires a victim to open or load a crafted DSM file whose header declares more than 240 PATT chunks or whose patt_len value wraps, defeating the missing nPat bound against MAX_PATTERNS. Impact is bounded to availability (process crash) with limited integrity effect and no confidentiality disclosure, and no public exploit code was identified at time of analysis; a public technical write-up of the defect exists, and the risk converges on a medium-severity memory-safety issue rather than a top-tier priority.
RemediationAI
No vendor-released patch was identified at time of analysis, so remediation depends on mitigation until an upstream fix lands. The most direct measure is to apply a source-level bounds check so that nPat is rejected once it exceeds MAX_PATTERNS (i.e. abandon parsing when the declared pattern count exceeds 240 or when patt_len wraps), mirroring the missing validation in src/load_dsm.cpp; teams that vendor or package libmodplug can carry this patch themselves, at the trade-off of maintaining a local fork. Where patching is impractical, disable DSM (and ideally other legacy module) parsing in any application that does not legitimately need it, eliminating the vulnerable code path entirely. For workflows that must process untrusted module files, isolate parsing in a separate low-privilege, sandboxed process with memory and crash-recovery limits so a heap-corruption crash cannot affect the parent or host; this adds architectural complexity and latency but contains the availability impact. Pre-scanning or rejecting untrusted DSM files with more than 240 PATT chunks, or with malformed/wrapping length fields, before handing them to libmodplug is a useful but weak control since it depends on the validator being at least as strict as the parser. Consult https://www.vulncheck.com/advisories/libmodplug-through-0.8.9.1-heap-out-of-bounds-write-via-csoundfile-readdsm and the upstream repository for any subsequent fix, and note that exact fixed versions are not confirmed from the available data.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
libmodplug is a library for decoding legacy tracker/module music formats, and its DSM (Digital Sound Module) loader lives in CSoundFile::ReadDSM() in src/load_dsm.cpp. The loader reads the DSM header, iterates PATT (pattern) chunks, and increments an internal pattern counter (nPat) without ever validating it against the MAX_PATTERNS ceiling - the vulnerable logic is the pattern-count handling referenced around lines 130-139 of the upstream source. Because nPat is unbounded, a file declaring more than 240 PATT chunks, or a patt_len value that wraps around, drives the parser to write past the end of a heap allocation. The root-cause class is CWE-787 (out-of-bounds write), and the defect maps to the affected CPE cpe:2.3:a:konstanty_bialkowski:libmodplug:*:*:*:*:*:*:*:*, i.e. the upstream Konstanty Bialkowski project. There is no authentication or network exposure inherent to the library itself; the attack surface is any application that parses attacker-supplied module files with the affected code path.
Know when Libmodplug gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
File must be opened locally by a victim (AV:L, UI:R), no privileges needed (PR:N); impact is a crash (A:H) with limited heap-write integrity effect (I:L) and no data disclosure (C:N).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
libmodplug through 0.8.9.1 contains a heap-based out-of-bounds write in CSoundFile::ReadDSM() in src/load_dsm.cpp because nPat is never checked against MAX_PATTERNS. Attackers can supply a crafted DSM file with over 240 PATT chunks or a wrapping patt_len value to corrupt heap memory and crash the consuming process.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
More in Libmodplug
View allInteger overflow in the abc_set_parts function in load_abc.cpp in libmodplug 0.8.8.4 and earlier allows remote attackers
Multiple heap-based buffer overflows in the (1) abc_MIDI_drum and (2) abc_MIDI_gchord functions in load_abc.cpp in libmo
Crafted AMS (Velvet Studio) module files can crash any application that uses libmodplug 0.8.9.1 or earlier by triggering
Out-of-bounds read in libmodplug through 0.8.9.1 allows a local attacker to cause the library to read one byte before th
Crafted ABC Music Format files cause uncontrolled resource consumption in libmodplug up to and including 0.8.9.1, where
EUVD-2026-102525
GHSA-rxvf-jg5h-5fv5
NVD
CVE.org
EPSS
Exploit-DB