Live › vulnerability › CVE-2026-119727
A malformed H.265 video file can make GStreamer's H.265 parser write past the end of a fixed-size array during parsing. The result is memory corruption and an application crash, and the sources limit the impact to denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 19:25 UTC. All times on this page are UTC.
Applications that use GStreamer's gst-plugins-bad H.265 parser to open video files, which can be triggered when such an application is given an attacker-supplied H.265 file. The sources do not give affected version ranges or a fix. Systems that never parse untrusted H.265 media through GStreamer can skip it.
No product ranges from the sources yet.
Unknown from the sources.
No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A flaw was found in GStreamer's gst-plugins-bad H.265 video parser. When parsing a specially crafted H.265 bitstream containing a Screen Content Coding (SCC) extension with certain palette predictor initializer settings, an integer underflow in the upper-bound computation allows the parser to accept an out-of-range value for the number of palette predictor entries. This causes the parser to write beyond the end of a fixed-size array, resulting in memory corruption and an application crash. Successful exploitation requires an attacker to provide a malformed H.265 media file to a vulnerable application, and is limited to a denial-of-service impact.
This page as .md · .json · in your agent: get_signal("CVE-2026-119727")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.