# CVE-2026-120243: FFmpeg 2.0 through 9.0.2 Information Disclosure via G2M Kempf Palette


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 1 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-120243, ECHO-a9d0-af6a-a402, GHSA-hcx6-ffr8-ff2w, UBUNTU-CVE-2026-120243

## What is CVE-2026-120243?

CVE-2026-120243 is a medium-severity vulnerability in FFmpeg, published on 1 Nov 2026. 

### Official description

FFmpeg 2.0 through 9.0.2 contains a use of uninitialized variable vulnerability in the Go2Meeting decoder that allows attackers to leak stack memory through out-of-range palette indices. Attackers can craft a G2M3/G2M4 stream with a short Kempf palette so kempf_restore_buf() copies uninitialized stack bytes, including pointers or stack guards, into decoded output.

Weakness: CWE-457 (Use of Uninitialized Variable)

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


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

Upgrade to a fixed version.

## Is CVE-2026-120243 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120243 is a medium-severity vulnerability in FFmpeg, published on 1 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120243 in the wild and no public exploit code.

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

## Sources

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

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