# CVE-2026-73434: Gstreamer1-plugins-good: gstreamer: out-of-bounds read in avidemux vprp video field descriptor parsing

> An out-of-bounds read in GStreamer's AVI parser allows attackers to crash applications via crafted media files, requiring an upgrade to the library.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 23 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-73434, ECHO-a321-5a7e-9f85, GHSA-wfhj-v65x-vjp5, MINI-j32m-jx3j-wx5q, UBUNTU-CVE-2026-73434

## What is CVE-2026-73434?

CVE-2026-73434 is a medium-severity memory corruption vulnerability in Gstreamer Gstreamer, published on 12 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in GStreamer gst-plugins-good (avidemux). In gst_avi_demux_riff_parse_vprp(), the number of available gst_riff_vprp_video_field_desc entries is calculated by dividing the remaining buffer size by the attacker-controlled vprp->fields value, rather than by sizeof(gst_riff_vprp_video_field_desc). This can cause the parser to treat more field descriptors as available than fit in the input buffer, resulting in out-of-bounds reads. Processing a crafted AVI via playbin/decodebin can crash the application (denial of service). Fixed upstream in gst-plugins-good 1.28.6 (GStreamer-SA-2026-0072).

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

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

It affects 2 products.


Products: Gstreamer Gstreamer, Redhat Enterprise Linux.

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

Upgrade to a fixed version.

## Is CVE-2026-73434 being exploited?

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

## Other vulnerabilities in Gstreamer Gstreamer

- [CVE-2026-3083](https://insights.sbomify.com/CVE-2026-3083/): GStreamer rtpqdm2depay Out-Of-Bounds Write Remote Code Execution Vulnerability (high 8.8)
- [CVE-2026-3085](https://insights.sbomify.com/CVE-2026-3085/): GStreamer rtpqdm2depay Heap-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-37328](https://insights.sbomify.com/CVE-2023-37328/): GStreamer PGS File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-37329](https://insights.sbomify.com/CVE-2023-37329/): GStreamer SRT File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-38103](https://insights.sbomify.com/CVE-2023-38103/): GStreamer RealMedia File Parsing Integer Overflow Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73434 is a medium-severity memory corruption vulnerability in Gstreamer Gstreamer, published on 12 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-73434 in the wild and no public exploit code.

Affected product: Gstreamer Gstreamer. 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-73434/ (Markdown: https://insights.sbomify.com/CVE-2026-73434/index.md)
```

## Sources

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

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