GStreamer H.266 Codec Parser Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. Interaction with this library is required to exploit this vulnerability but attack vectors may vary depending on the implementation.
The specific flaw exists within the parsing of decoding units. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28839.
Security readout for executives and security teams
Plain-English summary
CVE-2026-3081 is a high-severity memory corruption flaw in GStreamer’s H.266 codec parser. A crafted media input could cause code execution inside the application using GStreamer. Business risk depends on where GStreamer processes untrusted media, such as uploaded files, streams, or user-opened content.
Executive priority
Treat this as a high-priority patching and exposure review item, especially for media-processing services. It is not marked KEV in the provided bundle, but potential code execution in user-facing parsing workflows warrants timely remediation.
Technical view
The flaw is a stack-based buffer overflow while parsing H.266 decoding units. User-supplied length is not properly validated before data is copied into a fixed-size stack buffer, enabling possible arbitrary code execution in the current process. The CVSS 3.0 vector is 7.8, with user interaction required.
Likely exposure
Most likely exposed systems are applications, services, or desktop workflows that use affected GStreamer code to parse H.266 media from untrusted sources. The bundle does not confirm affected package versions beyond a referenced GStreamer commit/hash and vendor references.
Exploitation context
ZDI describes remote attackers executing code on affected GStreamer installations, but interaction with the library is required and attack vectors vary by implementation. The bundle says KEV is false, so there is no provided evidence of known active exploitation.
Researcher notes
Evidence supports a parser length-validation bug leading to stack overflow and possible RCE. Public details in the bundle do not establish broad product version ranges, exploit availability, or active exploitation. Validate impact through upstream commit analysis and distribution advisories.
Mitigation direction
Check GStreamer and operating-system vendor advisories for fixed releases containing the referenced commit.
Prioritize updates where GStreamer processes untrusted uploads, streams, attachments, or user-downloaded media.
Limit or disable H.266 parsing in high-risk paths until vendor-fixed packages are deployed.
Run media-processing workloads with least privilege and isolation where operationally feasible.
Track Red Hat and distribution advisories for package-specific impact and remediation status.
Validation and detection
Inventory applications and services that link to or package GStreamer.
Identify whether those systems parse H.266 or VVC media from untrusted sources.
Compare installed GStreamer builds against vendor fixed versions or the referenced upstream commit.
Review media-processing logs and crash reports for suspicious H.266 parser failures.
Confirm distribution-specific status using Red Hat or relevant vendor CVE pages.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-120 · source CWE mapping
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.