Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Supply crafted H.266 bitstream to custom app
  2. Exploit
    Reach DCI parser in libgstcodecparsers
  3. Execution
    Reserved field accepted, bounds check fails
  4. Impact
    Out-of-bounds write corrupts memory or crashes process

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a third-party application that directly invokes the vulnerable DCI parsing function in GStreamer's libgstcodecparsers (H.266/VVC) library; the description explicitly states no standard GStreamer pipeline element reaches this code path, so default GStreamer installations and typical playback pipelines are NOT exploitable. The attacker must deliver a specially crafted H.266 bitstream whose DCI reserved field carries an illegal value that the parser incorrectly accepts. Limiting factors: dependence on a non-standard API consumer sharply narrows the attack surface, and impact is bounded to memory corruption/crash (I:L/A:L) with no confidentiality loss and no demonstrated code-execution path in the provided data.

Impact

Red Hat rates this CVSS 6.5 (Medium) with vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L - network-reachable, no privileges, no user interaction, but only Low integrity and Low availability impact and no confidentiality impact, consistent with a bounded out-of-bounds write (CWE-787) that most realistically yields a crash. The single most important mitigating signal is in the description itself and directly tempers the network-vector optics: 'No standard GStreamer pipeline element currently invokes the affected code path,' meaning a default GStreamer install is not exploitable and an attacker needs a third-party application that explicitly calls the vulnerable DCI parsing API in libgstcodecparsers. No EPSS probability, CISA KEV listing, or public exploit was provided in the input, so exploitation status is: no public exploit identified at time of analysis. Net: this is a real but modest-priority memory-safety bug - patch it in normal cycles, but the CVSS network vector overstates practical exposure because the vulnerable code path is not reachable through standard pipelines; treat AV:N as 'reachable only via custom API consumers,' not 'remotely exploitable out of the box.' Verify affected GStreamer versions and fix with the Red Hat advisory, as no fixed version is present in the supplied data.

Exploit ScenarioDerived

An attacker crafts a malicious H.266/VVC bitstream containing a manipulated DCI reserved field and submits it to a third-party media application that directly invokes libgstcodecparsers' DCI parsing function (not a standard GStreamer pipeline). The parser accepts the illegal reserved value and writes past the bounds of an internal structure, corrupting memory or crashing the process. No public exploit code is identified in the provided data, and exploitation is constrained to applications that reach this specific API.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

An out-of-bounds write in GStreamer's H.266/VVC Decoding Capability Information (DCI) parser inside libgstcodecparsers allows a remote attacker to crash or corrupt memory in any third-party application that directly calls the affected parsing API by supplying a crafted H.266 bitstream whose reserved DCI field carries an illegal value the parser wrongly accepts. Red Hat rates it CVSS 6.5 (Medium, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L) - network-reachable, unauthenticated and requiring no user interaction per the supplied vector, but with only Low integrity and Low availability impact and no confidentiality loss, consistent with a bounded out-of-bounds write (CWE-787). Exposure is sharply limited: the description states no standard GStreamer pipeline element invokes this code path, so default GStreamer installations and ordinary playback pipelines are not exploitable, and no public exploit has been identified at time of analysis.

RemediationAI

No vendor-released patch or exact fixed version is identified in the provided data; patch status is therefore unconfirmed and should be tracked through the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-100229 and the associated Bugzilla entry at https://bugzilla.redhat.com/show_bug.cgi?id=2541471, applying updated gstreamer1-plugins-bad-free (and upstream GStreamer) packages as soon as they are published rather than assuming a fix is already available. Because the vulnerable DCI parsing routine is not reachable from any standard GStreamer pipeline element, the most effective near-term compensating control is at the API-consumer level: any application that directly calls the libgstcodecparsers H.266/VVC DCI parser should stop feeding it untrusted bitstreams, validate or reject DCI NAL units whose reserved fields fall outside the specification-permitted values before invoking the parser, or drop H.266/VVC input entirely until a fix ships - the trade-off being loss of H.266 capability for that application. Media-ingestion gateways and transcoding front ends can alternatively block or quarantine H.266/VVC content at the perimeter or run the parsing process in a sandboxed, resource- and privilege-limited worker so that a successful out-of-bounds write degrades to a contained crash rather than memory corruption in a privileged context; this costs throughput and may require changes to process architecture. Generic hardening such as ASLR, hardened allocators and crash-only supervision reduces the reliability of turning the write into control-flow hijack but does not remove the underlying bug, and since the assessed vector shows no confidentiality impact and no demonstrated code-execution path, effort should be prioritized on patching rather than on speculative exploit mitigation.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw lives in libgstcodecparsers, the codec bitstream parsing helper library shipped by GStreamer (packaged in Red Hat Enterprise Linux as part of gstreamer1-plugins-bad-free), specifically in the H.266/VVC parsing code that decodes the DCI (Decoding Capability Information) NAL unit. H.266, also known as Versatile Video Coding (VVC), is the successor to H.265/HEVC and its DCI structure contains reserved fields whose values are constrained by the specification; the parser fails to reject an out-of-range reserved value and consequently indexes/writes past the end of an internal structure, the classic memory-safety failure class described by CWE-787 (Out-of-bounds Write). Per the supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L) the exploit is remotely triggerable without authentication or user interaction against a host process, but impact is confined to Low integrity and Low availability - i.e., memory corruption leading most plausibly to a crash rather than a demonstrated code-execution or data-disclosure path. Importantly, the vulnerable routine is a library API entry point rather than a pipeline element, so exploitation depends on a third-party or custom application that calls the H.266 DCI parser directly on untrusted input; the CPE data associating the issue with Red Hat Enterprise Linux 7, 8, 9 and 10 reflects that the affected library ships across all supported RHEL streams, not that the base OS exercises the code path by default.

Know when Gstreamer gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (redhat) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
vuln.today AI 6.5 MEDIUM

Crafted bitstream needs no privileges or interaction, but impact is a bounded OOB write giving only low integrity/availability loss and no confidentiality; reachability caveat (non-standard API) noted separately, not scored.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
Red Hat 6.5 LOW

Primary rating from Vendor (redhat).

CVSS VectorVendor: redhat

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

DescriptionCVE.org

A flaw was found in GStreamer's H.266 codec parser library (libgstcodecparsers). An out-of-bounds write vulnerability exists in the DCI parsing function, where a reserved field value is incorrectly accepted, causing the parser to write beyond the bounds of an internal structure. An attacker could exploit this by providing a specially crafted H.266 bitstream to a third-party application that uses this library API, potentially causing a crash or memory corruption. No standard GStreamer pipeline element currently invokes the affected code path.

Threat Intelligence Overview

EPSS Score
0.4%
Top 71% exploitable
Prevalence
High
GStreamer ships broadly across Linux/RHEL, though H.266 DCI path rarely reached
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
High
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Affected Products (CPE)CVE.org

cpe:2.3:a:red_hat:red_hat_enterprise_linux_10:*:*:*:*:*:*:*:*
cpe:2.3:a:red_hat:red_hat_enterprise_linux_7:*:*:*:*:*:*:*:*
cpe:2.3:a:red_hat:red_hat_enterprise_linux_8:*:*:*:*:*:*:*:*
cpe:2.3:a:red_hat:red_hat_enterprise_linux_9:*:*:*:*:*:*:*:*
CVE-2016-9636 CRITICAL POC
9.8 Jan 27

Heap-based buffer overflow in the flx_decode_delta_fli function in gst/flx/gstflxdec.c in the FLIC decoder in GStreamer

CVE-2016-9635 CRITICAL POC
9.8 Jan 27

Heap-based buffer overflow in the flx_decode_delta_fli function in gst/flx/gstflxdec.c in the FLIC decoder in GStreamer

CVE-2016-9634 CRITICAL POC
9.8 Jan 27

Heap-based buffer overflow in the flx_decode_delta_fli function in gst/flx/gstflxdec.c in the FLIC decoder in GStreamer

CVE-2016-9808 HIGH POC
7.5 Jan 13

The FLIC decoder in GStreamer before 1.10.2 allows remote attackers to cause a denial of service (out-of-bounds write an

CVE-2019-9928 HIGH
8.8 Apr 24

A heap-based buffer overflow vulnerability exists in GStreamer's RTSP connection parser that allows remote attackers to

CVE-2025-47219 HIGH POC
8.1 Aug 07

A heap buffer over-read vulnerability exists in GStreamer's isomp4 plugin that allows reading past allocated memory boun

CVE-2022-1920 HIGH POC
7.8 Jul 19

An integer overflow vulnerability in the GStreamer multimedia framework's matroska demuxer allows heap memory corruption

CVE-2022-2122 HIGH POC
7.8 Jul 19

A critical integer overflow vulnerability in GStreamer's qtdemux element allows attackers to trigger denial of service o

CVE-2022-1924 HIGH POC
7.8 Jul 19

A critical integer overflow vulnerability in the GStreamer multimedia framework's Matroska (MKV) demuxer can cause denia

CVE-2022-1922 HIGH POC
7.8 Jul 19

An integer overflow vulnerability in GStreamer's Matroska demuxer can cause denial of service or potentially heap memory

CVE-2022-1921 HIGH POC
7.8 Jul 19

An integer overflow vulnerability in GStreamer's AVI demux element allows attackers to trigger a heap overwrite when par

CVE-2022-1925 HIGH POC
7.8 Jul 19

A heap overflow vulnerability exists in GStreamer's matroskaparse element due to an integer overflow in the gst_matroska

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy