cve.bz

CVE-2026-86476 Gstreamer1-plugins-base: gst-plugins-base: heap buffer overflow via unvalidated gstvideometa plane extents in gst_video_frame_map_id and video_meta_deserialize

8.4 highEPSS 0.2%Fix available

High (8.4) in red hat. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw was found in gst-plugins-base. A heap buffer overflow can be triggered when processing video buffers whose attached GstVideoMeta metadata declares plane strides and offsets that exceed the actual backing memory allocation. The metadata is not range-checked during deserialization, and the video frame mapping code does not verify that the declared plane geometry fits within the buffer before allowing consumers to read or write video data. A local attacker who controls the sending side of a GStreamer inter-process IPC pipeline can deliver a crafted buffer carrying fabricated strides, causing the receiving process to read or write beyond heap boundaries. Successful exploitation can cause a denial of service or potentially allow code execution within the affected process.

Severity

CVSS 3.1

8.4 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
Assigned by
redhat (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Red Hat Red Hat Enterprise Linux 10: fixed in 0:1.26.7-4.el10_3.1
  • Red Hat Red Hat Enterprise Linux 10.2 Extended Update Support: fixed in 0:1.26.7-2.el10_2.3
  • Ubuntu, Red Hat, AlmaLinux, Rocky Linux: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-86476 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-86476?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-86476?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-86476 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • red hat:red hat enterprise linux 10
  • red hat:red hat enterprise linux 10.2 extended update support
  • red hat:red hat enterprise linux 6
  • red hat:red hat enterprise linux 7
  • red hat:red hat enterprise linux 8
  • red hat:red hat enterprise linux 9

Versions

From the CNA's record in the CVE List.

Fixed in

ProductFixed in
Red Hat Enterprise Linux 100:1.26.7-4.el10_3.1
Red Hat Enterprise Linux 10.2 Extended Update Support0:1.26.7-2.el10_2.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14gst-plugins-base1.0no fix listedDEBIAN-CVE-2026-86476
Ubuntu22.04:LTSgst-plugins-base1.01.20.1-1ubuntu0.9USN-9094-1
Ubuntu24.04:LTSgst-plugins-base1.0no fix listedUBUNTU-CVE-2026-86476 USN-9094-1
Ubuntu26.04:LTSgst-plugins-base1.01.28.2-1ubuntu0.3UBUNTU-CVE-2026-86476 USN-9094-1
Ubuntu26.10gst-plugins-base1.01.28.7-1ubuntu0.2UBUNTU-CVE-2026-86476 USN-9094-1
UbuntuPro:16.04:LTSgst-plugins-base1.01.8.3-1ubuntu0.3+esm7USN-9094-1
UbuntuPro:18.04:LTSgst-plugins-base1.01.14.5-0ubuntu1~18.04.3+esm6USN-9094-1
UbuntuPro:20.04:LTSgst-plugins-base1.01.16.3-0ubuntu1.4+esm5USN-9094-1
UbuntuPro:22.04:LTSgst-plugins-bad1.01.20.3-0ubuntu1.1+esm4USN-9094-1
UbuntuPro:24.04:LTSgst-plugins-bad1.01.24.2-1ubuntu4+esm3USN-9094-1
Red Hatenterprise_linux:10.3gstreamer1-plugins-base, gstreamer1-plugins-base-devel, gstreamer1-plugins-base-tools and 3 more0:1.26.7-4.el10_3.1RHSA-2026:98600
Red Hatenterprise_linux_eus:10.2gstreamer1-plugins-base, gstreamer1-plugins-base-devel, gstreamer1-plugins-base-tools and 3 more0:1.26.7-2.el10_2.3RHSA-2026:99033
AlmaLinux10gstreamer1-plugins-base, gstreamer1-plugins-base-devel, gstreamer1-plugins-base-tools1.26.7-4.el10_3.1ALSA-2026:98600
Rocky Linux10gstreamer1-plugins-base, gstreamer1-plugins-base-devel, gstreamer1-plugins-base-tools and 3 more0:1.26.7-4.el10_3.1RLSA-2026:98600
Azure Linux3gstreamer1-plugins-baseno fix listedAZL-108306
Alpaquita23, 25, streamgst-plugins-baseno fix listedBELL-CVE-2026-86476

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat is evaluating product impact for gst-plugins-base (libgstvideo) across supported streams. Upstream has confirmed the issue is valid and expects a fix in GStreamer 1.28.8 (target approximately October 2026). Coordinated public disclosure date is pending confirmation from upstream. The practical cross-process attack path requires GStreamer 1.24 or later with the unixfd plugin (unixfdsink/unixfdsrc), which serializes GstVideoMeta over Unix domain sockets. Upstream states the unixfd plugin is not used by software packaged in Red Hat Enterprise Linux or major Linux distributions, and the affected elements are not engaged automatically, limiting real-world exposure. Earlier GStreamer versions lack the unixfd IPC path but may still be affected by the underlying libgstvideo validation gap for in-process use. Red Hat Enterprise Linux builds ship with standard compiler hardening (PIE, Full RELRO, stack protector, _FORTIFY_SOURCE), and ASLR is enabled by default. These controls increase the difficulty of reliable code execution beyond denial of service but do not prevent the heap out-of-bounds access itself. On platforms where GStreamer runs inside a sandbox (for example Flatpak without shared IPC namespace), cross-process unixfd communication may be restricted, reducing exposure to the untrusted-sender scenario.

Red Hat's mitigation

If inter-process video sharing via unixfd is not required, build or deploy GStreamer without the unixfd plugin (for example meson option -Dgst-plugins-bad:unixfd=disabled, or omit libgstunixfd.so from the GStreamer plugin directory). Upstream confirms this is the only practical mitigation for the cross-process attack path and notes the unixfd plugin is not currently used by Red Hat-packaged or major distribution software. Operational policy to avoid connecting receiver pipelines to Unix socket endpoints controlled by untrusted local processes provides equivalent protection without rebuilding. This does not address the underlying validation gap in libgstvideo when attacker-controlled GstVideoMeta is supplied in-process.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10gstreamer1-plugins-base-0:1.26.7-4.el10_3.1Fixed 2026-11-11RHSA-2026:98600
Red Hat Enterprise Linux 6gstreamer-plugins-baseAffected
Red Hat Enterprise Linux 7gstreamer1-plugins-baseAffected
Red Hat Enterprise Linux 7gstreamer-plugins-baseAffected
Red Hat Enterprise Linux 8gstreamer1-plugins-baseAffected
Red Hat Enterprise Linux 9gstreamer1-plugins-baseAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-86476.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

References

Check your stackJSON