# CVE-2026-56208: Libaom: libaom: heap buffer overflow in av1 encoder first-pass stats buffer via lap mode

> Heap buffer overflow in libaom AV1 encoder allows attackers to cause denial of service or potentially execute code via crafted encoder configurations.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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-56208, ECHO-c281-5876-5f69, GHSA-mgv2-4j37-m3x6, ROOT-OS-DEBIAN-11-CVE-2026-56208, UBUNTU-CVE-2026-56208

## What is CVE-2026-56208?

CVE-2026-56208 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 vulnerability was found in libaom, the reference AV1 codec implementation. A flaw in the AV1 encoder's Look-Ahead Processing (LAP) mode causes the first-pass stats ring buffer wrap-around guard to be bypassed when g_lag_in_frames is set to 1 or higher. This results in a 232-byte out-of-bounds write on every encoded frame after the second, corrupting adjacent heap objects. An attacker who can influence encoder configuration in a transcoding service or WebRTC session could exploit this to cause a denial of service (process crash) or potentially achieve code execution.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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


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

Apply the vendor's patch.

## Is CVE-2026-56208 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56208 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-56208 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-56208/ (Markdown: https://insights.sbomify.com/CVE-2026-56208/index.md)
```

## Sources

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

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