Is there a public exploit for CVE-2026-56209?

No public exploit for CVE-2026-56209 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-56209?

CVE-2026-56209 scores CVSS 7.1 (v3.1), rated high. EPSS puts the chance of exploitation in the next 30 days at 0.64%.

What does CVE-2026-56209 affect?

CVE-2026-56209 affects Red Hat Red Hat OpenShift AI 3.5, Red Hat OpenShift AI 3.4, Red Hat Enterprise Linux AI 3.4 for RHEL 9, Red Hat Enterprise Linux AI 3.3, Red Hat AI Inference Server 3.2, Red Hat Enterprise Linux AI 3.5 for RHEL 9.

7.1 High

An arbitrary address write vulnerability was found in libaom, the reference AV1 codec implementation.

CVE-2026-56209

An arbitrary address write 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 an attacker to inject an arbitrary pointer into the cyclic refresh map field via crafted image pixel values. The encoder then writes approximately 1,200 bytes at the attacker-controlled address. This is fully deterministic and does not require a separate information leak. An attacker who can supply frames to a network-facing libaom encoder with SVC enabled could exploit this for denial of service or potential code execution.

Assessment

CVSS: 7.1 (v3.1)
Severity: High
EPSS: 0.64% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 19 June 2026
Last updated: 4 November 2026
Affected: Red Hat · Red Hat AI Inference Server 3.2 · Red Hat AI Inference Server 3.3 · Red Hat Enterprise Linux AI 3.3 · Red Hat Enterprise Linux AI 3.3 for RHEL 9
Assigner: redhat

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H

At the source

EUVD (ENISA)

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 8 + 5? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-56209