Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft MS ADPCM WAV with odd samplesPerBlock
-
DeliveryDeliver file to victim or ingest pipeline
-
Exploitsox/libsox decodes fmt chunk and block
-
ExecutionOut-of-bounds 16-bit write past heap buffer
-
ImpactHeap corruption causes crash or memory tampering
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 that a victim process an attacker-supplied MS ADPCM-encoded WAV file in which the fmt chunk's samplesPerBlock field is set to an odd value; this is the specific trigger. The affected code path is MS ADPCM WAV decoding in SoX (sox CLI) or any downstream application linking libsox, so any product version through 14.4.2 that accepts untrusted WAV input is in scope. LIMITING FACTORS: the attack vector is local/file-based (AV:L) and requires user interaction (UI:P) - the attacker cannot trigger it remotely without the victim opening or feeding the file to sox/libsox; no authentication or special privileges are needed (PR:N). Risk concentrates in automated services that decode untrusted audio; purely interactive, trusted-input usage is far less exposed. |
| Impact | This is a moderate-severity memory-corruption flaw (CWE-787, heap out-of-bounds write) whose signals are internally consistent rather than conflicting. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:H, score 6.9) describes a local, low-complexity, unauthenticated issue that nonetheless requires user interaction - i.e. a victim must open or process an attacker-supplied file. There is no network vector; exploitation is file-driven, so real-world risk is bounded by how the crafted WAV reaches a victim. Public exploit code exists (POC=YES, reported by VulnCheck), which raises the practical likelihood of opportunistic use, but there is NO CISA KEV listing and NO EPSS score provided, so there is no evidence of active, widespread exploitation - the signals point to a disclosed-but-not-yet-weaponized bug. The impact profile is skewed toward availability (VA:H, denial of service via heap corruption / crash) with only partial integrity impact (VI:L, a partially controlled 16-bit write) and no confidentiality impact (VC:N); the description does not substantiate reliable arbitrary code execution, only a partially controlled out-of-bounds write. Net: a genuine but not top-priority issue - prioritize for any service that auto-ingests untrusted audio via libsox, deprioritize for interactive desktop-only use. |
| Exploit ScenarioDerived | An attacker crafts a malicious MS ADPCM WAV file whose fmt chunk specifies an odd samplesPerBlock value and delivers it to a victim (e.g. as an email attachment, upload, or media file processed by a backend). When the victim runs sox on the file or an application built on libsox decodes it, lsx_ms_adpcm_block_expand_i() writes a partially controlled 16-bit sample past the allocated heap buffer, corrupting heap memory. Public exploit/writeup material is available, so the trigger condition is documented and reproducible. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Heap out-of-bounds write in SoX (the sox CLI and any application linking libsox) through 14.4.2 allows a crafted MS ADPCM WAV file with an odd samplesPerBlock value in its fmt chunk to write a partially controlled 16-bit sample past the heap buffer allocated by wav_ms_adpcm_fmt(), corrupting adjacent memory. Triggering the flaw requires the victim to open or submit the malicious file to sox/libsox (local attack vector, user interaction), but no authentication or privileges are needed; publicly available exploit code exists and no CISA KEV listing is present. The assessed impact is low integrity and high availability (CVSS 3.1 6.9, CWE-787), with exposure concentrated in automated audio-processing services that decode untrusted files.
RemediationAI
No vendor-released patch version is identified in the available data - the references point only to upstream source lines in chirlu/sox (adpcm.c lines 144-166 and wav.c lines 250-251) rather than a tagged fix, so remediation should focus on compensating controls. If you build SoX from source, monitor the upstream repository for a commit or release that bounds-checks samplesPerBlock and rebuild once the fix lands. Until then, block untrusted MS ADPCM WAV files at ingestion: validate that the fmt chunk's samplesPerBlock is even and that blockAlign matches expected block sizing, rejecting malformed files (this can break legitimate playback of unusual but valid ADPCM files). Where MS ADPCM support is not required, compile SoX without MS ADPCM decoding or disable the relevant format handler so crafted files cannot reach lsx_ms_adpcm_block_expand_i(); where it is required, run sox/libsox under a sandboxed worker with a restrictive memory limit and heap protections, and restrict which users or services can submit audio to automated decode pipelines. Consult the VulnCheck advisory (https://www.vulncheck.com/advisories/sox-through-14.4.2-heap-out-of-bounds-write-via-ms-adpcm-wav-decoding) for updates.
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
The flaw is a heap-based out-of-bounds write (CWE-787) in the Microsoft ADPCM decoder, specifically lsx_ms_adpcm_block_expand_i() in src/adpcm.c (referenced upstream lines 144-166) and the allocation performed by wav_ms_adpcm_fmt() in src/wav.c (upstream lines 250-251). MS ADPCM WAV files describe block layout in the fmt chunk via samplesPerBlock and blockAlign; when samplesPerBlock is odd, the decoder's per-block expansion loop computes sample indices that exceed the heap buffer sized from the declared layout and writes a 16-bit sample past the end of that buffer. The value written is only partially controlled by the attacker, so this is a memory-corruption primitive rather than a straightforward code-execution exploit, but it can corrupt heap metadata or adjacent objects. CPE cpe:2.3:a:sox:sox:* indicates all versions of SoX are affected up to and including 14.4.2, and any downstream libsox consumer that parses untrusted WAV input inherits the risk.
Know when Sox 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
Local file parsing with victim interaction (AV:L, UI:R) and no privileges (PR:N); partially controlled OOB write gives I:L, heap corruption yields A:H, with no confidentiality impact (C:N).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
SoX through 14.4.2 contains a heap out-of-bounds write vulnerability in lsx_ms_adpcm_block_expand_i() in src/adpcm.c, triggered by an odd samplesPerBlock value in the WAV fmt chunk. Attackers can supply a crafted MS ADPCM WAV file to sox or any libsox consumer to write a partially controlled 16-bit sample past the heap buffer allocated by wav_ms_adpcm_fmt().
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.
EUVD-2026-102284
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB