# CVE-2026-2921: GStreamer RIFF Palette Integer Overflow Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code via integer overflow in GStreamer's RIFF palette handling when processing malicious AVI files.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** 13 Mar 2026
- **Updated:** 21 Jul 2026
- **Also known as:** AZL-79974, BELL-CVE-2026-2921, CLSA-2026-1776334207, CLSA-2026-1776778859, CLSA-2026-1785308941, DEBIAN-CVE-2026-2921, DLA-4514-1, DSA-6167-1, GHSA-g7gw-mp9w-623w, MINI-ggj8-46v2-cjjh, OESA-2026-1755, OESA-2026-1756, OESA-2026-1757, OESA-2026-1758, OESA-2026-1820, OESA-2026-1821, UBUNTU-CVE-2026-2921

## What is CVE-2026-2921?

CVE-2026-2921 is a high-severity vulnerability in Gstreamer Gstreamer, published on 13 Mar 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

GStreamer RIFF Palette Integer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. Interaction with this library is required to exploit this vulnerability but attack vectors may vary depending on the implementation.

The specific flaw exists within the handling of palette data in AVI files. The issue results from the lack of proper validation of user-supplied data, which can result in an integer overflow before writing to memory. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28854.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Gstreamer Gstreamer.

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

Apply the vendor's patch.

## Is CVE-2026-2921 being exploited?

There is no known exploitation of CVE-2026-2921 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-2921 and fix it if it is affected.

What it is: CVE-2026-2921 is a high-severity vulnerability in Gstreamer Gstreamer, published on 13 Mar 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-2921 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-2921/ (Markdown: https://insights.sbomify.com/CVE-2026-2921/index.md)
```

## Sources

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

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