# CVE-2026-30999: Memory corruption in n/a

> Attackers can cause a Denial of Service in FFmpeg via a crafted input triggering a heap buffer overflow in av_bprint_finalize.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-30999, ECHO-8cbe-edcd-eee7, GHSA-jj28-p98r-mwqj, JLSEC-2026-651, MINI-3hv9-48fj-46p2, UBUNTU-CVE-2026-30999

## What is CVE-2026-30999?

CVE-2026-30999 is a high-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A heap buffer overflow in the av_bprint_finalize() function of FFmpeg v8.0.1 allows attackers to cause a Denial of Service (DoS) via a crafted input.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Upgrade to a fixed version.

## Is CVE-2026-30999 being exploited?

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

## Other vulnerabilities in Ffmpeg Ffmpeg

- [CVE-2013-0864](https://insights.sbomify.com/CVE-2013-0864/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0872](https://insights.sbomify.com/CVE-2013-0872/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0873](https://insights.sbomify.com/CVE-2013-0873/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-4265](https://insights.sbomify.com/CVE-2013-4265/): Null dereference in n/a (critical 10.0)
- [CVE-2011-3937](https://insights.sbomify.com/CVE-2011-3937/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30999 is a high-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-30999 in the wild and no public exploit code.

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

## Sources

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

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