CVE-2026-56210 — CVE & Security Advisory Radar

🎯 CVE-2026-56210 🇪🇺 EUVD

📄 .md Alle CVEs anzeigen ✕

CVE-2026-56210 | 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

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).

Klassifikation & Betroffenheit:

Red Hat Red Hat OpenShift AI 3.4 patch: 1787077779Red Hat Enterprise Linux AI 3.3 for RHEL 9 patch: 0:3.14.0-1.el9aiRed Hat Enterprise Linux AI 3.4 for RHEL 9 patch: 0:3.14.0-1.el9aiRed Hat AI Inference Server 3.2 patch: 1787884873Red Hat OpenShift AI 3.4 patch: 1787076778Red Hat OpenShift AI 3.4 patch: 1786611800Red Hat AI Inference Server 3.2 patch: 1787860580Red Hat Hardened Images patch: 3.14.0-0.1.hum1

Improper Control of Generation of Code ('Code Injection') 🎯 Medium

The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

🛡️ Empfohlene Mitigation: Refactor your program so that you do not have to dynamically generate code.

Vollständige Definition bei MITRE ➔

⚔️ Typische Angriffsmuster (CAPEC):

CAPEC-35 · Leverage Executable Code in Non-Executab… (Very High) CAPEC-77 · Manipulating User-Controlled Variables (Very High) CAPEC-242 · Code Injection (High)

🎯 ATT&CK-Techniken (Kill-Chain-Verhalten):

T1027.006 · Obfuscated Files or Information: H… T1027.009 · Obfuscated Files or Information: E… T1564.009 · Hide Artifacts: Resource Forking

🧩 Ähnliche Schwachstellen (Hersteller/Klasse/Score-Band):

CVE-2026-10649 8.6 CVE-2026-5367 8.6 CVE-2026-1761 8.6 CVE-2026-0719 8.6 CVE-2024-11218 8.6

📚 Referenzen & Quellen:

🇪🇺 Original-Eintrag (ENISA EUVD) 🇺🇸 NVD-Eintrag

Ausnutzungs-Zeitleiste:

Reserviert 2026

Veröffentlicht 06/2026

Heute 19.09.

CVSS-Vektor-Analyse: 7.1

AV · Angriffsvektor Netzwerk

AC · Komplexität Gering

PR · Privilegien Keine

UI · Interaktion Erforderlich

S · Scope Unverändert

C · Vertraulichkeit Gering

I · Integrität Keine

A · Verfügbarkeit Hoch

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

Veröffentlicht:19.06.2026

Aktualisiert:01.09.2026 13:19

Assigner (CNA):redhat

EUVD-ID:EUVD-2026-38046

Quellen: 🇪🇺 EUVD-Datenbank (ENISA) + 🇺🇸 NVD-Anreicherung · 24-h-Cache

CWE-94: Code Injection ✓ Offizieller Patch / Advisory verfügbar

💡 Gegenmaßnahme: Sicherheits-Update des Herstellers zeitnah einspielen und Netzwerksegmentierung prüfen.

Tier	2026-08-30	2026-09-18
≥90 %	0	0
≥50 %	0	0
≥10 %	0	0
<10 %	300	300

EPSS

31%

CVE-2026-56210 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

Red Hat

CVE-2026-56210 | 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

CWE-94: Code Injection ✓ Offizieller Patch / Advisory verfügbar

💡 Gegenmaßnahme: Sicherheits-Update des Herstellers zeitnah einspielen und Netzwerksegmentierung prüfen.

19.06.2026

🛡️ Details ➔

Zero-Day & Vulnerability Intelligence Hub