# CVE-2026-120457: libaec through 1.1.7 Out-of-Bounds Read via m_se_decode() Second Extension Decoder


- **Severity:** Medium 5.8 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** AZL-112580, DEBIAN-CVE-2026-120457, ECHO-02df-4108-6f70, GHSA-6vjr-59w2-48mg, UBUNTU-CVE-2026-120457, openSUSE-SU-2026:12461-1

## What is CVE-2026-120457?

CVE-2026-120457 is a medium-severity vulnerability in Deutsches Klimarechenzentrum libaec, published on 2 Nov 2026. 

### Official 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.

Weakness: CWE-196 (Unsigned to Signed Conversion Error)

## Which versions are affected by CVE-2026-120457?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libaec` | openSUSE:Tumbleweed | All versions | 1.1.8-1.1 |

## How do I fix CVE-2026-120457?

Upgrade to a fixed version.

## Is CVE-2026-120457 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120457 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120457 and fix it if it is affected.

What it is: CVE-2026-120457 is a medium-severity vulnerability in Deutsches Klimarechenzentrum libaec, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120457 exists.

Affected product: Deutsches Klimarechenzentrum libaec. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120457/ (Markdown: https://insights.sbomify.com/CVE-2026-120457/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120457
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120457
- OSV: https://osv.dev/vulnerability/CVE-2026-120457

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120457/
Summaries are generated and may contain mistakes; the official description above is the record.
