dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2026-53701

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An out-of-bounds write vulnerability was found in GStreamer's H.266/VVC PPS picture partition parser in gst-plugins-bad. In the multi-slice-in-tile processing of gst_h266_parser_parse_picture_partition() (gsth266parser.c), the loop iterates without checking that the slice index stays within bounds, writing past three fixed-size arrays (slice_height_in_ctus, slice_top_left_ctu_x, slice_top_left_ctu_y) in the GstH266PPS structure. While the initial proof-of-concept demonstrated a 4-byte out-of-bounds write, the code permits larger writes across multiple iterations. A crafted H.266/VVC media file can trigger this vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An out-of-bounds write vulnerability exists in GStreamer's H.266/VVC PPS picture partition parser (gsth266parser.c) where the gst_h266_parser_parse_picture_partition() function iterates through a loop without validating that the slice index remains within the bounds of three fixed-size arrays (slice_height_in_ctus, slice_top_left_ctu_x, slice_top_left_ctu_y) in the GstH266PPS structure. A crafted H.266/VVC media file can trigger writes past array boundaries, potentially leading to memory corruption.

MitigationUpdate gst-plugins-bad to a version containing the bounds-check fix for gst_h266_parser_parse_picture_partition(), or implement input validation to reject H.266/VVC streams with partition parameters exceeding the fixed array sizes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if GStreamer gst-plugins-bad is installed
    Run 'pkg-config --modversion gst-plugins-bad-1.0' or check your system's package manager for gst-plugins-bad (e.g., 'dpkg -l | grep gst-plugins-bad' on Debian/Ubuntu, 'rpm -qa | grep gst-plugins-bad' on RHEL/CentOS)
    Affected if gst-plugins-bad is not installed or the package cannot be found, the vulnerability does not apply to your environment
  2. Determine the version of gst-plugins-bad
    Compare the installed version against the version that contains the bounds-check fix for gst_h266_parser_parse_picture_partition() in gsth266parser.c; use 'gst-inspect-1.0 vvcparse 2>/dev/null' to confirm the vvcparse element is available
    Affected if The installed version is older than the patched version and H.266/VVC parsing support is present
  3. Confirm H.266/VVC parsing support is enabled
    Run 'gst-inspect-1.0 | grep -i vvc' to list available VVC-related elements; specifically check for 'vvcparse' element which handles PPS picture partition parsing
    Affected if The vvcparse element is present and loaded, meaning GStreamer can parse H.266/VVC bitstreams containing picture partition information
  4. Check for presence of vulnerable gsth266parser.c code
    Locate the gsth266parser.c file in your GStreamer installation (typically in gst-libs/gst/codecs/ or gst/vvcparser/) and verify the gst_h266_parser_parse_picture_partition() function lacks bounds checking on slice index before array access to slice_height_in_ctus, slice_top_left_ctu_x, and slice_top_left_ctu_y
    Affected if The source code shows no bounds validation on the slice index variable before writing to the three arrays in the GstH266PPS structure

Your environment is affected if GStreamer gst-plugins-bad with H.266/VVC (VVC) parsing support is installed and the version predates the bounds-check fix for gst_h266_parser_parse_picture_partition().

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update gst-plugins-bad to a version containing the bounds-check fix for gst_h266_parser_parse_picture_partition(), or implement input validation to reject H.266/VVC streams with partition parameters exceeding the fixed array sizes.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53701 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53701 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data