EUVD-2026-46062
GHSA-wp47-28f7-9775
Severity by source
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Local malicious-file parsing bug requiring victim to open a file (AV:L/UI:R), no privileges needed, and memory corruption yields full C/I/A impact in the user's context.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
Lifecycle Timeline
2DescriptionCVE.org
DNG SDK versions 1.7.1 2536 and earlier are affected by a Stack-based Buffer Overflow vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
AnalysisAI
Arbitrary code execution in Adobe DNG SDK version 1.7.1 (build 2536) and earlier arises from a stack-based buffer overflow triggered when parsing a maliciously crafted image file, allowing an attacker to run code in the context of the current user. Applications that embed the DNG SDK to decode Digital Negative (DNG) raw camera files are affected, and successful exploitation requires the victim to open the malicious file. No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV.
Technical ContextAI
The Adobe DNG SDK is a C++ library that reads, writes, and validates Digital Negative (DNG) files - Adobe's open raw-image container based on the TIFF/EP structure - and is embedded in raw-processing pipelines and imaging applications. The root cause is CWE-121 (Stack-based Buffer Overflow): during parsing of attacker-controlled file structures (image metadata, tag lengths, or pixel/tile data), a fixed-size stack buffer is written past its bounds, corrupting the stack frame including saved return addresses and enabling control-flow hijack. The affected component per CPE is cpe:2.3:a:adobe:dng_sdk, meaning any downstream product statically or dynamically linking the vulnerable SDK inherits the exposure regardless of the host application's own code.
RemediationAI
Upgrade to the fixed Adobe DNG SDK release published in Adobe security bulletin APSB26-67 (https://helpx.adobe.com/security/products/dng-sdk/apsb26-67.html); the input does not include the exact patched build number, so Patch available per vendor advisory and the fixed version should be taken directly from that bulletin rather than assumed. Developers who embed the SDK must rebuild and redistribute their applications against the patched library, since patching the host app alone will not remediate a statically linked SDK. Until updated, reduce risk by not opening DNG or raw image files from untrusted sources, restricting or sandboxing applications that auto-process raw files (for example previewers or ingest pipelines that parse files without explicit user action), and blocking untrusted DNG attachments at mail/web gateways; the trade-off is disruption to legitimate photography and imaging workflows that rely on automatic raw handling.
Heap-based buffer overflow in Adobe DNG SDK versions 1.7.1 (build 2536) and earlier enables arbitrary code execution in
Out-of-bounds read in Adobe DNG SDK 1.7.1 build 2536 and earlier exposes sensitive process memory when a victim opens a
Out-of-bounds memory read in Adobe DNG SDK 1.7.1 build 2536 and earlier enables sensitive process memory disclosure when
Out-of-bounds read in Adobe DNG SDK 1.7.1 build 2536 and earlier exposes sensitive process memory contents when a victim
Null Pointer Dereference in Adobe DNG SDK versions 1.7.1 build 2536 and earlier allows an attacker to crash any applicat
Out-of-bounds write in Adobe DNG SDK 1.7.1 2502 and earlier causes application denial-of-service through memory corrupti
Same weakness CWE-121 – Stack-based Buffer Overflow
View allShare
External POC / Exploit Code
Leaving vuln.today