# CVE-2026-38345: Denial of service in n/a

> Attackers can cause a denial of service in FFmpeg by providing crafted input that triggers a division-by-zero error in the scaling utility.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Aug 2026
- **Updated:** 2 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-38345, GHSA-rgh2-m3vh-23hp, UBUNTU-CVE-2026-38345

## What is CVE-2026-38345?

CVE-2026-38345 is a medium-severity denial of service vulnerability in n/a, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Division-by-Zero vulnerability in the ff_sws_init_single_context function (/libswscale/utils.c) of FFmpeg N-122528-gdd2976b9e1 allows attackers to cause a Denial of Service (DoS) via a crafted input.

Weakness: CWE-369 (Divide By Zero)

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


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

Upgrade to a fixed version.

## Is CVE-2026-38345 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-38345 is a medium-severity denial of service vulnerability in n/a, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, 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-38345 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-38345/ (Markdown: https://insights.sbomify.com/CVE-2026-38345/index.md)
```

## Sources

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

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