# CVE-2025-22920: Memory corruption in n/a

> Attackers can cause a denial of service in FFmpeg by supplying a crafted media file that triggers a heap buffer overflow.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Feb 2025
- **Updated:** 19 Feb 2025
- **Also known as:** GHSA-7qgp-q3fg-4c39, UBUNTU-CVE-2025-22920

## What is CVE-2025-22920?

CVE-2025-22920 is a medium-severity memory corruption vulnerability in n/a, published on 18 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A heap buffer overflow vulnerability in FFmpeg before commit 4bf784c allows attackers to trigger a memory corruption via supplying a crafted media file in avformat when processing tile grid group streams. This can lead to a Denial of Service (DoS).

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

## Which versions are affected by CVE-2025-22920?


## How do I fix CVE-2025-22920?

Apply the vendor's patch.

## Is CVE-2025-22920 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22920 and fix it if it is affected.

What it is: CVE-2025-22920 is a medium-severity memory corruption vulnerability in n/a, published on 18 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-22920 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-2025-22920/ (Markdown: https://insights.sbomify.com/CVE-2025-22920/index.md)
```

## Sources

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

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