Heap-based buffer overflow in libjpeg-turbo merged upsampling (h2v2_merged_upsample_internal)
A heap-based buffer overflow was identified in libjpeg-turbo’s merged upsampling path, specifically in the h2v2_merged_upsample_internal() function in jdmrgext.c. The issue is reachable when decompressing specially crafted 12-bit lossless JPEG images containing out-of-range 12-bit samples; because the sample data type range exceeds the valid sample range in this mode, malformed sample values can lead to memory corruption during merged upsampling. Successful triggering can result in a segmentation fault and/or heap buffer overflow during decompression, causing the consuming application to crash.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in Windows Win32K (GRFX) with an 'Exploitation Less Likely' rating per the content.
A heap-based overflow in libjpeg-turbo referenced under Windows Win32K - GRFX (no additional details provided in the content).
A heap-based overflow vulnerability in libjpeg-turbo that can lead to remote code execution.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.