libaec through 1.1.7 Out-of-Bounds Read via m_se_decode() Second Extension Decoder
- Exploited
- Proof of concept public, per CISA
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Caller uses the streaming decoder with an output buffer smaller than one output block, which selects the slow decoder path. Compressed stream selects the Second Extension sub-option in a low-entropy block. Stream contains a first fundamental sequence with a zero run of at least 2^31 bits before its terminating one bit. Tested against libaec v1.1.7; current main branch was also reported as affected.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- 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? →
- 26/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
- Fix
- Fix or patch referenced
- 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
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
libaec through 1.1.7 contains an out-of-bounds read vulnerability in m_se_decode() in src/decode.c that allows attackers to bypass a signed bounds check via an overlong fundamental sequence. Attackers can supply a crafted CCSDS 121.0/SZIP stream with 2^31 or more zero bits to crash the decoder or leak adjacent memory into decoded samples.
What to do
Check whether your setup matches what the bug needs.
Caller uses the streaming decoder with an output buffer smaller than one output block, which selects the slow decoder path. Compressed stream selects the Second Extension sub-option in a low-entropy block. Stream contains a first fundamental sequence with a zero run of at least 2^31 bits before its terminating one bit. Tested against libaec v1.1.7; current main branch was also reported as affected.Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Deutsches Klimarechenzentrum libaec
through 1.1.7
Evidence 6
- Patch
- Report
- Repository
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120457
What does this mean?
A crafted compressed stream can make libaec read past the end of a heap buffer while decoding. The main effect is a denial of service through a process crash, and adjacent heap memory may be exposed through decoded output samples.Source: github.com
Am I affected, and how do I check?
Versions through libaec 1.1.7 are listed as affected, and the reporter also said the current main branch was affected. The exposure needs the streaming decoder with an output buffer smaller than one output block, and a stream that uses the Second Extension sub-option in a low-entropy block with a first fundamental sequence holding a zero run of at least 2^31 bits. To check a version, look at the libaec release in use.Source: github.com
What should I do about it?
No fixed version is listed in the checked facts, so no upgrade target can be given from this record. Check the libaec project for a release newer than 1.1.7 or a commit that addresses this issue.Source: github.com
Is it 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data