Vulnerabilities

Vulnerability · CVE-2026-53702

A stack buffer overflow flaw was found in the GStreamer H.265 codec parser library (gst-plugins-bad).

Published Jun 11, 2026 · catalog updated Oct 16, 2026 · A stack buffer overflow

Check if you run it

No confirmed exploitation is on record for CVE-2026-53702. EPSS is 0.40%. Act only if a listed version of A stack buffer overflow is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (A stack buffer overflow).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium6.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.40%
Remediation
Advisory link
Affected products
Debian:12 gst-plugins-bad1.0 · Debian:13 gst-plugins-bad1.0 · Debian:14 gst-plugins-bad1.0

A stack buffer overflow flaw was found in the GStreamer H.265 codec parser library (gst-plugins-bad). When parsing a buffering period SEI message, the parser uses an incorrect loop bound derived from cpb_cnt_minus1[i] (the loop index) instead of the sub-layer 0 CPB count cpb_cnt_minus1[0] from the referenced Sequence Parameter Set. A crafted H.265 video file or stream can cause the parser to write beyond the bounds of stack-allocated CPB delay arrays, resulting in a crash or potential stack memory corruption.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Debian:12 gst-plugins-bad1.00 → 1.22.0-4+deb12u8
  • Debian:13 gst-plugins-bad1.01.26.10-1, 1.26.10-2, 1.26.2-3
  • Debian:14 gst-plugins-bad1.00 → 1.28.3-1

How to fix CVE-2026-53702

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-53702. EPSS is 0.40%. Act only if a listed version of A stack buffer overflow is installed.

Which versions are affected?

Compare what you have installed with 0 → 1.22.0-4+deb12u8, 1.26.10-1, 1.26.10-2, 1.26.2-3, 0 → 1.28.3-1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.40%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 11, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    A stack buffer overflow flaw was found in the GStreamer H.265 codec parser library (gst-plugins-bad). When parsing a buffering period SEI message, the parser uses an incorrect loop bound derived from cpb_cnt_minus1[i] (the loop index) instead of the sub-layer 0 CPB count cpb_cnt_minus1[0] from the referenced Sequence Parameter Set. A crafted H.265 video file or stream can cause the parser to write

  2. Oct 16, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    gst-plugins-bad1.0 fixed in 1.22.0-4+deb12u8; gst-plugins-bad1.0 fixed in 1.28.3-1

  3. Oct 16, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    gst-plugins-bad1.0 fixed in 1.22.0-4+deb12u8

  4. Oct 16, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    gst-plugins-bad1.0 fixed in 1.28.3-1

  5. Oct 16, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    A stack buffer overflow flaw was found in the GStreamer H.265 codec parser library (gst-plugins-bad). When parsing a buffering period SEI message, the parser uses an incorrect loop bound derived from cpb_cnt_minus1[i] (the loop index) instead of the sub-layer 0 CPB count cpb_cnt_minus1[0] from the referenced Sequence Parameter Set. A crafted H.265 video file or stream can cause the parser to write

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.