SDL_mixer 3.1.2 through 3.2.4 Stack-based Buffer Overflow via FetchXLaw() in WAV Decoder
Affects SDL_mixer 3.1.2 through 3.2.4 when decoding WAV files that use A-law or mu-law encoding. No fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected SDL_mixer versions are 3.1.2 through 3.2.4 The WAV file must use A-law or mu-law encoding (format tag 0x0006 or 0x0007)
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
SDL_mixer versions 3.1.2 through 3.2.4 have a stack-based buffer overflow in the WAV decoder's handling of A-law and mu-law files. An attacker can exploit it locally, without logging in, by getting a user to open a crafted WAV file, which can crash the application or potentially lead to code execution.
Read the original description
SDL_mixer 3.1.2 through 3.2.4 contains a stack-based buffer overflow vulnerability in FetchXLaw() of src/decoder_wav.c when decoding A-law or mu-law WAV files. Attackers can supply a crafted WAV file whose doubly-offset float expansion overwrites about 1 KB of adjacent stack memory, causing crashes or potentially code execution.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 8.5
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected SDL_mixer versions are 3.1.2 through 3.2.4 The WAV file must use A-law or mu-law encoding (format tag 0x0006 or 0x0007)Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- libsdl-org SDL_mixer
From 3.1.2 · through 3.2.4
Evidence 8
- Patch
- Patch
- Report
- Repository
- Repository
Show all 8 sourcesShow fewer sources
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-122328
Is CVE-2026-122328 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted WAV file can overflow a buffer on the stack in SDL_mixer's WAV decoder, in the FetchXLaw() path. The advisory says this can crash the program and could potentially lead to code execution.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-122328?
SDL_mixer: from 3.1.2 through 3.2.4.Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are SDL_mixer 3.1.2 through 3.2.4. The vulnerable code path is reached only when a WAV file uses MULAW encoding (format tag 0x0007) or ALAW encoding (format tag 0x0006). The SDL_mixer version can be checked in the build files or the installed package's version information.Source: vulncheck.com, github.com
How do I fix CVE-2026-122328?
The checked facts do not name a fixed release. Check the vendor's release notes or advisory for a version later than 3.2.4 and move to it when it is available.Source: vulncheck.com, github.com