# CVE-2026-52719: Gstreamer1-plugins-bad-free: gstreamer: out-of-bounds read via jpeg segment length validation in va decoder

> A remote attacker can cause a crash or disclose memory contents by tricking a user into opening a crafted JPEG file processed by the GStreamer VA decoder.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Jun 2026
- **Updated:** 30 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-52719, ECHO-c6e4-fb80-f88a, GHSA-33x5-f9c4-3q24, SUSE-SU-2026:2743-1, SUSE-SU-2026:2744-1, UBUNTU-CVE-2026-52719, openSUSE-SU-2026:21204-1

## What is CVE-2026-52719?

CVE-2026-52719 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An out-of-bounds read vulnerability was found in the VA JPEG decoder in GStreamer's gst-plugins-bad. The JPEG parser reads a segment length value from the bitstream without validating it against available data. A remote attacker could trick a user into opening a specially crafted JPEG file, causing downstream parsing to read beyond the provided input buffer, leading to a crash or potential information disclosure.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-52719?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gstreamer-plugins-bad` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 1.22.0-150500.3.31.1 |
| `gstreamer-plugins-bad` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 1.22.0-150500.3.31.1 |
| `gstreamer-plugins-bad` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 1.24.0-150600.4.6.1 |
| `gstreamer-plugins-bad` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP7 | All versions | 1.24.0-150600.4.6.1 |
| `gstreamer-plugins-bad` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 1.24.0-150600.4.6.1 |
| `gstreamer-plugins-bad` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 1.22.0-150500.3.31.1 |
| `gstreamer-plugins-bad` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 1.24.0-150600.4.6.1 |
| `gstreamer-plugins-bad` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 1.22.0-150500.3.31.1 |
| `gstreamer-plugins-bad` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 1.24.0-150600.4.6.1 |
| `gstreamer-plugins-bad` | openSUSE:Leap 16.0 | All versions | 1.26.7-160000.2.1 |

## How do I fix CVE-2026-52719?

Apply the vendor's patch.

## Is CVE-2026-52719 being exploited?

There is no known exploitation of CVE-2026-52719 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-52719 and fix it if it is affected.

What it is: CVE-2026-52719 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-52719 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-52719/ (Markdown: https://insights.sbomify.com/CVE-2026-52719/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-52719
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-52719
- OSV: https://osv.dev/vulnerability/CVE-2026-52719

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-52719/
Summaries are generated and may contain mistakes; the official description above is the record.