Skip to main content
Public proof of concept

CVE-2026-86476

A public proof of concept exists; no exploitation attested.

  • Published2026-10-14
  • WeaknessCWE-787

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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

dates in UTC
  1. 2026-10-1410:17CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-86476?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-86476?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-86476 yet.

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

read 2026-10-23 19:25 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
1 repository, unverified0xSemizzz/CVE-2026-86476
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2026-10-14
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.18.4read 2026-10-23
  • CNAweakness (CWE)CWE-787read 2026-10-23
  • FIRST EPSSEPSS score0.2 %2026-10-22
  • PoC-in-GitHubproof of concept1read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2026-10-14
Last Modified
2026-10-14
NVD status
Awaiting Analysis

Frequently asked questions

What is CVE-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 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.

Is CVE-2026-86476 actively exploited?

Active exploitation of CVE-2026-86476 has not been confirmed. Its EPSS score was 0.2% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-86476?

CVE-2026-86476 has a CVSS v3 base score of 8.4 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month