ZeroDay Findings
Sign inSign up

Findings

CVE-2026-86476

A flaw was found in gst-plugins-base.

Published Oct 14, 2026 · updated Oct 15, 2026

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.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 14, 2026 · NIST NVD

    Detected

    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

  2. Oct 14, 2026 · NIST NVD

    Updated

    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

  3. Oct 14, 2026 · NIST NVD

    Updated

    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

  4. Oct 15, 2026 · OSV.dev

    Updated

    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

Affected

  • Debian:12 gst-plugins-base1.01.22.0-3, 1.22.0-3+deb12u1, 1.22.0-3+deb12u2
  • Debian:13 gst-plugins-base1.01.26.10-1, 1.26.2-1, 1.26.2-1+deb13u1
  • Debian:14 gst-plugins-base1.01.26.10-1, 1.26.2-1, 1.26.3-1

Sources

  • CVE.orgCVE-2026-86476

    Official CVE identifier

    cve.org
  • FIRST EPSSCVE-2026-86476

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDCVE-2026-86476

    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 deseriali

    nvd.nist.gov
  • OSV.devDEBIAN-CVE-2026-86476
    osv.dev

References