# CVE-2026-46471: Information disclosure in n/a

> An attacker can disclose heap memory contents by crafting a malicious MP4 file parsed by the GStreamer isomp4 plugin.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **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:** 16 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-46471, ECHO-dec4-644f-c531, GHSA-5vvw-9383-fwx7, UBUNTU-CVE-2026-46471

## What is CVE-2026-46471?

CVE-2026-46471 is a medium-severity vulnerability in n/a, published on 16 Oct 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

An issue was discovered in GStreamer gst-plugins-good before 1.28.2. While parsing an MP4 file, the isomp4 plugin's qtdemux_parse_uuid function may read past the end of a heap-allocated buffer, allowing an attacker to disclose heap memory contents.

Weakness: CWE-126 (Buffer Over-read)

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


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

Upgrade to a fixed version.

## Is CVE-2026-46471 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46471 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46471 is a medium-severity vulnerability in n/a, published on 16 Oct 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46471 exists.

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

## Sources

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

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