EUVD-2026-86282
GHSA-6f7j-6h98-j3ww
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft MP3 with malicious APEv2 tag-size
-
DeliveryDeliver file to target application
-
ExploitTrigger integer overflow in mp3dec_skip_id3v1()
-
ExecutionCause out-of-bounds access/heap corruption
-
ImpactCrash or execute code in host process
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK
1 technique across 1 tactic: Execution 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 with minimp3 (at/around commit ea99364f) to parse an attacker-controlled MP3 file whose APEv2 tag contains a crafted tag-size value that overflows the size arithmetic in mp3dec_skip_id3v1(). The limiting factor is that this is a library-level file-parsing bug: an attacker cannot reach it directly over the network unless a service ingests untrusted audio; in most deployments a user or automated pipeline must open/decode the malicious file (effective user interaction), contradicting the input vector's UI:N. Impact severity also depends on how the downstream application handles the corrupted parse (crash vs. exploitable corruption) and the platform's memory protections. |
| Impact | The NVD/MITRE CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, 9.8 Critical) presents this as trivially remote-exploitable with no user interaction, but that rating appears inflated for the actual defect: minimp3 is a passive file-parsing library, and the overflow triggers in mp3dec_skip_id3v1() while parsing an APEv2 tag-size field in an input file. Real-world exploitation therefore requires an application to decode an attacker-supplied MP3/tagged file, which in practice implies user interaction (UI:R) or at minimum a data-flow where crafted media reaches the parser - the CVSS omission of UI:N does not match a client-side decoder. This is corroborated by the low-signal exploitation data: EPSS is 0.15% (3rd percentile), there is NO CISA KEV listing, and no confirmed public exploit - only a GitHub issue (#151) that likely contains a technical report or crash reproducer but not weaponized code. No SSVC decision data was provided. Net: this is a genuine memory-safety bug (CWE-190 integer overflow, plausibly leading to OOB access/heap corruption) in a widely-embedded C library, but it is NOT a mass-exploitation, network-service priority - it is a client/embedded file-parsing risk. Treat the 9.8 as an overstatement and prioritize based on whether your product feeds untrusted audio into minimp3. |
| Exploit ScenarioDerived | An attacker crafts an MP3 file with a malicious APEv2 tag whose declared tag-size field overflows the integer arithmetic in mp3dec_skip_id3v1(), then delivers it to a victim application (media player, game, transcoding pipeline, or embedded firmware) that uses minimp3. When the file is decoded, the overflow leads to out-of-bounds memory access or heap corruption, causing a crash or potentially memory disclosure/code execution in the host process. A GitHub issue (#151) exists and likely includes a crashing reproducer, but no confirmed weaponized exploit was identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 29, 2026
Integer overflow in minimp3's mp3dec_skip_id3v1() tag-parsing routine allows a crafted APEv2 tag-size field inside an MP3 file to corrupt internal size arithmetic, which can lead to memory corruption in any application that decodes untrusted audio with a build at or around commit ea99364f. The CVSS vector supplied with the record is 9.8 (AV:N/AC:L/PR:N/UI:N), but our assessment lowers user interaction to UI:R: minimp3 is a passive single-header decoder library, so a victim or automated ingestion pipeline must open or feed the malicious file before the overflow is reachable, and there is no direct network attack surface in the library itself. No public exploit code has been identified at time of analysis, EPSS is low at 0.15% (3rd percentile), and the CVE is not listed in CISA KEV, so exploitation is unconfirmed and real-world risk depends on whether the consuming application processes hostile media.
RemediationAI
No vendor-released patch was identified at time of analysis and no fixed version number is available in the provided data, so the immediate action is to monitor the upstream tracker at https://github.com/lieff/minimp3/issues/151 (referenced from the NVD record at https://nvd.nist.gov/vuln/detail/CVE-2026-88365) and update the vendored copy of minimp3 as soon as a fix commit lands - the library is header-only, so re-vendoring the corrected file is the whole upgrade. Until then, the most effective compensating control is to reject or strip metadata before decoding: pre-validate APEv2 and ID3v1 tag-size fields against the remaining file length and a sane maximum, and refuse or truncate files whose declared tag sizes exceed the actual buffer, accepting that this discards tag metadata that some applications may rely on for artwork or track information. Second, isolate decoding in a separate, low-privilege process or container with a strict seccomp profile, no network egress, and resource limits, so a corrupted parse results in a contained crash rather than host compromise - this adds latency and operational complexity but is the only control that holds if the overflow is steered toward code execution. Third, enable compiler and allocator hardening for any binary embedding minimp3 (stack protector, FORTIFY_SOURCE, full RELRO, hardened malloc such as hardened_malloc or Scudo) and consider running parsers under sanitizer builds in staging to detect the overflow early. Finally, for deployments that must process untrusted audio at scale, consider migrating to an actively maintained decoder such as libmpg123 or an ffmpeg-based pipeline, weighing the integration and licensing effort against the maintenance risk of a minimal single-file library.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
minimp3 is a minimal, dependency-free, single-file C MP3 decoder that is commonly vendored into other projects rather than linked as a system library. The vulnerable function mp3dec_skip_id3v1() walks over ID3v1 and APEv2 metadata blocks embedded in or appended to an MP3 stream before audio decoding begins, reading a size field from the tag header and using it to advance through the buffer. The flaw is CWE-190 (Integer Overflow): the attacker-controlled APEv2 tag-size value is used in size arithmetic without sufficient bounds checking, so the computed size or offset can wrap, causing the parser to advance to an unintended location and subsequently read or write outside the intended tag/audio region. The record also carries a Buffer Overflow tag, consistent with the overflow of the size computation manifesting as an out-of-bounds memory access downstream. The provided CPE data is only a placeholder (cpe:2.3:a:n/a:n/a:*) and the ENISA EUVD affected-version list is likewise "n/a n/a", so exact version ranges cannot be enumerated from those feeds and must be derived from the upstream repository around commit ea99364f. Practical impact severity is heavily deployment-dependent: it is governed by how the consuming application handles a corrupted parse (clean crash versus memory corruption that can be steered), by the allocator and platform memory protections in place (ASLR, DEP, hardened allocators), and by whether the decoder runs with a memory-safe boundary.
Know when N A 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
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Crafted file can be delivered remotely (AV:N) but a decoder must process it, so UI:R rather than UI:N; integer overflow enabling memory corruption plausibly yields high C/I/A.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
3DescriptionCVE.org
minimp3 commit ea99364f contains an integer overflow vulnerability in mp3dec_skip_id3v1() when parsing the APEv2 tag-size field.
Executive ViewAI
CVE-2026-88365 is a critical memory-corruption flaw in minimp3, the single-header MP3 decoder embedded in applications and media-ingestion pipelines built at or around commit ea99364f, where a crafted APEv2 tag-size field in an MP3 file overflows internal size arithmetic. No vendor-released patch is available, so every product shipping that decoder build remains exposed until it is rebuilt against a fix or the tag-parsing path is hardened, and any team that accepts untrusted audio - mobile players, embedded playback, automated content pipelines - carries the risk. Leadership should treat this as a supply-chain remediation obligation rather than an active incident: no public exploit code has been identified at time of analysis, and the low EPSS (0.15%, 3rd percentile) and absence from CISA KEV mean real-world exposure depends entirely on whether the consuming application opens hostile media.
No vendor-released patch identified at time of analysis. Interim mitigations: sandbox and isolate the decoding process at low privilege with strict memory and syscall restrictions; disable or bypass ID3v1/APEv2 tag parsing where the application does not require tag metadata; pre-sanitize or strip tags from untrusted MP3 files before they reach minimp3; restrict accepted file types, origins, and sizes at ingestion boundaries; block untrusted MP3 ingestion entirely in high-value pipelines until a fix lands; and evaluate substituting a maintained, memory-hardened MP3 decoder. Monitor the upstream commit stream and vendor advisories for a fixed revision and rebuild immediately once released.
Threat Intelligence Overview
NVD
CVE.org
EPSS
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.
Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.
LibreNMS before 24.10.0 allows a remote attacker to execute arbitrary code via OS command injection involving AboutContr
Reachable assertion in Open5GS up to version 2.7.6 allows remote unauthenticated attackers to crash the Diameter CER han
A Command Injection issue in the payload build page in BYOB (Build Your Own Botnet) 2.0 allows attackers to execute arbi
Denial of service in Open5GS 2.7.6 and earlier allows network-adjacent attackers with low-privilege Diameter Gx peer acc
Denial of service in Open5GS HSS (Home Subscriber Server) versions 2.7.0 through 2.7.6 is triggered remotely by manipula
Remote command injection in Control Web Panel allows unauthenticated attackers to execute arbitrary OS commands as root
LINQPad before 5.52.01 Pro edition is vulnerable to Unsafe Deserialization in LINQPad.AutoRefManager::PopulateFromCache(
Remote code execution in dash-uploader (Python package for Plotly Dash) versions 0.1.0 through 0.7.0a2 allows unauthenti
Command injection in LiteLLM 1.18.10 lets attackers who can configure MCP (Model Context Protocol) servers supply arbitr
SQL injection in AzuraCast's backup restore flow (versions up to and including 0.23.7) lets an attacker achieve privileg
Arbitrary file read in Yu AI Code Mother v4.3 lets anonymous, remote attackers retrieve files outside the intended previ
Remote code execution in APScheduler (all versions through 3.10.x and 4.0.0a5) is achievable when applications deseriali
Exploit-DB