# CVE-2026-56210: Libaom: libaom: heap-buffer-overflow read via missing bounds check in ctrl_set_layer_id

> A heap-buffer-overflow in libaom allows attackers to leak memory or crash services via crafted SVC encoder parameters.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Jun 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-56210, ECHO-4013-f50e-8dfc, GHSA-xpjh-7q9g-cgj5, ROOT-OS-DEBIAN-11-CVE-2026-56210, UBUNTU-CVE-2026-56210

## What is CVE-2026-56210?

CVE-2026-56210 is a high-severity memory corruption vulnerability in Red Hat AI Inference Server, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A heap-buffer-overflow read vulnerability was found in libaom, the reference AV1 codec implementation. A missing bounds check in the SVC (Scalable Video Coding) layer ID control function allows setting a spatial_layer_id exceeding the configured number of layers. This causes an out-of-bounds heap read of approximately 40,728 bytes when computing a layer context array index. An attacker who can influence SVC encoder parameters in a network-facing service could exploit this for information disclosure (heap content leak) or denial of service (segmentation fault from hitting unmapped memory).

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2026-56210 being exploited?

There is no known exploitation of CVE-2026-56210 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56210 is a high-severity memory corruption vulnerability in Red Hat AI Inference Server, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-56210 in the wild and no public exploit code.

Affected product: Red Hat AI Inference Server. 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-56210/ (Markdown: https://insights.sbomify.com/CVE-2026-56210/index.md)
```

## Sources

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

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