CVE-2026-120244
Medium · 5.5CVSS
5.5
EPSS
0.1%
Published
Nov 1, 2026
CISA due date
—
Cloudanix analysis
A flaw in widely used video software can accidentally reveal hidden data from memory when opening certain image files, which might expose private information.
- Exploitation
- Requires User Interaction
- Attacker needs
- User Interaction
- Complexity
- Low
- Impact
- Data Exposure
- Component
- Library
- Class
- Information Disclosure
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Use of uninitialized resource in FFmpeg PCX decoder where truncated RLE scanlines in pcx_decode_frame() cause av_malloc() buffer contents to be copied into decoded output pixels, disclosing heap memory.
Why it matters to the business
Processing untrusted PCX images in media workflows can leak sensitive heap data, risking exposure of confidential information with minimal attacker effort.
How an attack unfolds
Attacker creates a PCX image with prematurely ending RLE data. When FFmpeg decodes it, pcx_decode_frame() copies uninitialized heap memory into visible pixels, allowing the attacker to inspect leaked contents from the decoded image.
How to fix it
Upgrade FFmpeg to a version newer than 9.0.2 containing the PCX decoder fix. Until patched, disable PCX support or restrict decoding to trusted sources only.
How to confirm the fix worked
Confirm FFmpeg version exceeds 9.0.2, then test with crafted truncated-RLE PCX samples to verify no uninitialized memory appears in output pixels.
Typical attack path
- Craft PCX image containing truncated RLE scanlines
- Deliver image to target application using vulnerable FFmpeg
- Trigger PCX decoding via pcx_decode_frame()
- Inspect decoded output for leaked heap memory contents
How to detect it
Review application logs for PCX file processing events; inspect decoded image outputs or crash dumps for unexpected non-image data patterns originating from heap buffers.
What your security team should do
- Prioritize upgrade of all FFmpeg installations within 30 days given public disclosure
- Block or sandbox untrusted PCX file processing in media pipelines
- Add PCX decoder logging to detect anomalous image handling
The record
FFmpeg 2.1 through 9.0.2 contains a use of uninitialized resource vulnerability in the PCX decoder that allows attackers to leak heap memory through truncated RLE scanlines. Attackers can craft a PCX image whose RLE data ends early, causing pcx_decode_frame() to copy uninitialized av_malloc() buffer contents into visible decoded pixels.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|
Related vulnerabilities
- CVE-2026-121227 Uninitialized resource in Skia in Google Chrome prior to 157.0.8103.38 allowed a remote… CWE-908
- CVE-2026-121213 Uninitialized resource in Images in Google Chrome prior to 157.0.8103.38 allowed a remote… CWE-908
- CVE-2026-121207 Uninitialized resource in Dawn in Google Chrome on on Mac prior to 157.0.8103.38 allowed… CWE-908
- CVE-2026-121176 Uninitialized resource in Media in Google Chrome prior to 157.0.8103.38 allowed a remote… CWE-908
- CVE-2026-121173 Uninitialized resource in WebGL in Google Chrome prior to 157.0.8103.38 allowed a remote… CWE-908
- CVE-2026-121143 Uninitialized resource in GPU in Google Chrome prior to 157.0.8103.38 allowed a remote… CWE-908
- CVE-2026-121095 Uninitialized resource in WebGL in Google Chrome prior to 157.0.8103.38 allowed a remote… CWE-908
- CVE-2026-121072 Uninitialized resource in Skia in Google Chrome prior to 157.0.8103.38 allowed a remote… CWE-908