Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft truncated Sun Raster file
-
DeliveryDeliver to victim for decoding
-
ExploitDecoder expands uncleared bitmap to PAL8
-
ExecutionStale heap bytes leaked into output
-
ImpactAttacker recovers disclosed memory
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Variable initialization
|
| Exploitation Conditions | Exploitation requires the victim to decode an attacker-supplied, deliberately TRUNCATED Sun Raster (.ras/.sun) image that uses 1-bit or 4-bit paletted format, which triggers the uncleared temporary bitmap in sunrast_decode_frame() to be expanded into PAL8 output (vulnerable code at libavcodec/sunrast.c around lines 188-194 in n9.0.2). Limiting factors: the victim must actively process the file (UI:P / local vector per CVSS), only this specific low-bit-depth paletted Sun Raster code path is affected, and the impact is confined to confidentiality - the attacker must additionally be able to observe the decoded output to recover the leaked heap bytes. Affected versions are FFmpeg 0.10 through 9.0.2; updating to the patched build is the fix per the vendor commits. |
| Impact | This is a moderate-severity information-disclosure flaw (CWE-908, use of uninitialized resource) rather than a top-priority emergency. The input CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N) scores 6.8 and tells a consistent story: exploitation requires local processing of an attacker-crafted file with passive user interaction, impacts confidentiality only (heap memory leak), and has no integrity or availability effect. There is no KEV listing, so this is NOT confirmed actively exploited; the vuln.today decision label is 'this_month' (routine remediation urgency, not act_now/emergency). No EPSS score was supplied, so widespread-exploitation probability cannot be quantified from the data. No public exploit code is identified - the references contain only the upstream fix PR, two patch commits, the vulnerable source lines, and a VulnCheck advisory, none of which is a working PoC. The signals are mutually consistent: a real but bounded issue whose impact is leakage of stale heap bytes (e.g. allocator words) into decoded output, not code execution or crash. One note for verification: the vector uses AV:L, yet FFmpeg frequently decodes media delivered over networks/streams, so some deployments may face a remote-ish delivery path even though the metric is scored local - confirm the delivery model for your environment. |
| Exploit ScenarioDerived | An attacker crafts a truncated 1-bit or 4-bit paletted Sun Raster image and delivers it to a victim who opens or transcodes it with an FFmpeg-based tool. When sunrast_decode_frame() expands the uncleared temporary bitmap into PAL8 pixels, stale heap contents (such as allocator metadata) are emitted into the decoded output, which the attacker can then read back. No public exploit code is identified at time of analysis, and exploitation requires the victim to process the malicious file (UI:P). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 01, 2026
FFmpeg 0.10 through 9.0.2 can leak heap memory when decoding a deliberately truncated 1-bit or 4-bit paletted Sun Raster (.ras/.sun) image. The bug is a use of uninitialized resource (CWE-908) in sunrast_decode_frame(): the temporary bitmap is never cleared, so when it is expanded into PAL8 pixels the decoded frame can contain stale heap bytes such as allocator words. Impact is confidentiality-only and requires the victim to process the crafted file and for the attacker to observe the decoded output; there is no public exploit identified at time of analysis, and the vendor has published upstream fix commits.
RemediationAI
Vendor-released patch: upstream fix commits 356a391bf57df2fb80fd61f2821c8c83d15ce180 and 66b6ca270b33fd74367d7d371f6de16ec664446e in libavcodec/sunrast.c, proposed via https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/24877; released patched version not independently confirmed beyond these commits, so build or update past 9.0.2 from the fixed tree and verify the row-clearing memset is present in sunrast_decode_frame(). Apply the commits with https://github.com/FFmpeg/FFmpeg/commit/356a391bf57df2fb80fd61f2821c8c83d15ce180 and https://github.com/FFmpeg/FFmpeg/commit/66b6ca270b33fd74367d7d371f6de16ec664446e, and track https://github.com/FFmpeg/FFmpeg for the release tag that carries them. Per the vendor commits, updating is the complete fix; no workaround is documented, and the exposure is narrowed by the fact that only truncated 1-bit or 4-bit paletted Sun Raster input reaches the vulnerable expansion path and the attacker must be able to read the decoded output to recover the leaked heap bytes.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw sits in libavcodec/sunrast.c, FFmpeg's decoder for the Sun Raster (SunOS rasterfile) image format, in the code path that handles 1-bit and 4-bit paletted images and expands them into PAL8 output (vulnerable lines roughly 188-194 in the n9.0.2 tree). CWE-908 (use of uninitialized resource) applies because the decoder allocates a temporary bitmap but does not initialize it before palette expansion; with a truncated input the parser stops early, leaving rows of the temporary buffer unpopulated, and those uninitialized bytes are then converted to output pixels. The upstream fix moves the end-pointer and x-coordinate setup ahead of the expansion loop and adds an explicit memset over the remaining rows so the buffer is zero-filled before conversion. The CVSS 4.0 vector supplied with the CVE (AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N) and the independent 3.1 assessment (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) agree that this is a local-vector, user-interaction-driven disclosure with no integrity or availability effect; the trigger requires that specific low-bit-depth paletted code path, not general Sun Raster decoding.
Know when Ffmpeg gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Victim must decode a crafted local file (AV:L, UI:R) with no privileges or added complexity (PR:N, AC:L); only heap memory is disclosed, so C:H and I/A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
FFmpeg 0.10 through 9.0.2 contains a use of uninitialized resource vulnerability in sunrast_decode_frame() that leaks heap memory when decoding truncated 1-bit and 4-bit paletted Sun Raster images. Attackers can craft a truncated Sun Raster file so the uncleared temporary bitmap is expanded into PAL8 pixels, exposing stale heap contents such as allocator words in decoded output.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in FFmpeg Decoder Uninitialized Memory Leaks
View all 5FFmpeg 2.x allows remote attackers to conduct cross-origin attacks and read arbitrary files by using the concat protocol
FFmpeg before 2.8.12, 3.0.x and 3.1.x before 3.1.9, 3.2.x before 3.2.6, and 3.3.x before 3.3.2 does not properly restric
FFmpeg 2.x allows remote attackers to conduct cross-origin attacks and read arbitrary files by using the subfile protoco
The av_reallocp_array function in libavutil/mem.c in FFmpeg before 2.0.1 has an unspecified impact and remote vectors re
cbs_jpeg_split_fragment in libavcodec/cbs_jpeg.c in FFmpeg 4.1 and 4.2.2 has a heap-based buffer overflow during JPEG_MA
Out-of-bounds heap write in FFmpeg's RASC video decoder (decode_dlta in libavcodec/rasc.c) allows attackers to corrupt m
Memory corruption in FFmpeg before 8.1 allows an attacker who can supply a crafted H.264/HEVC media file to corrupt heap
Integer Overflow vulnerability in function filter_sobel in libavfilter/vf_convolution.c in Ffmpeg 4.2.1, allows attacker
Integer Overflow vulnerability in function filter_robert in libavfilter/vf_convolution.c in Ffmpeg 4.2.1, allows attacke
Integer Overflow vulnerability in function filter_prewitt in libavfilter/vf_convolution.c in Ffmpeg 4.2.1, allows attack
Integer Overflow vulnerability in function filter16_sobel in libavfilter/vf_convolution.c in Ffmpeg 4.2.1, allows attack
Integer Overflow vulnerability in function filter16_roberts in libavfilter/vf_convolution.c in Ffmpeg 4.2.1, allows atta
EUVD-2026-114742
GHSA-c346-mwjq-88hv
NVD
CVE.org
VulDB
Exploit-DB