Skip to main content

Adobe DNG SDK CVE-2026-47927

| EUVDEUVD-2026-37132 MEDIUM
Out-of-bounds Read (CWE-125)
2026-06-16 adobe GHSA-q57c-73r4-6g5h
5.5
CVSS 3.1 · Vendor: adobe
Share

Severity by source

Vendor (adobe) PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
vuln.today AI
5.5 MEDIUM

File-based local attack (AV:L, UI:R) with no attacker privileges needed (PR:N); impact is memory disclosure only (C:H, I:N, A:N), unchanged scope.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
4.0 AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (adobe).

CVSS VectorVendor: adobe

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

1
Analysis Generated
Jun 16, 2026 - 19:10 vuln.today

DescriptionCVE.org

DNG SDK versions 1.7.1 2536 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to disclose sensitive information. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

AnalysisAI

Out-of-bounds read in Adobe DNG SDK 1.7.1 build 2536 and earlier exposes sensitive process memory contents when a victim opens a specially crafted DNG image file. The attacker requires no privileges of their own - the attack surface is entirely dependent on social engineering a user into opening a malicious file processed by any application embedding the vulnerable SDK. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, indicating no confirmed active exploitation.

Technical ContextAI

Adobe DNG SDK is a C++ library used by Adobe and third-party developers to parse and write Digital Negative (DNG) files, Adobe's publicly documented raw image format standard. The root cause is CWE-125 (Out-of-Bounds Read): during parsing of a DNG file, the SDK reads data beyond the allocated buffer boundary, likely due to insufficient validation of a length or offset field embedded in the malformed image structure. The result is that memory contents adjacent to the intended buffer - which may include pointers, keys, or other in-process sensitive data - are accessible to the attacker via the disclosed bytes. CPE cpe:2.3:a:adobe:dng_sdk:*:*:*:*:*:*:*:* covers the affected product range. The 'Buffer Overflow' tag in the source data likely reflects broader buffer mismanagement in the parser rather than a write-primitive overflow, as the confirmed CWE and impact are limited to read and disclosure. CVSS AV:L confirms the attack surface is file-system-based rather than network-exposed.

RemediationAI

Adobe has published security advisory APSB26-67 at https://helpx.adobe.com/security/products/dng-sdk/apsb26-67.html, which should be consulted for the exact patched SDK version, as the available input data does not independently confirm the specific fixed build number beyond the vulnerable ceiling of version 1.7.1 build 2536. Developers embedding the DNG SDK in their products should upgrade to the patched SDK version and rebuild and redistribute their applications to end users. As a compensating control prior to patching, any workflow that automatically processes untrusted DNG files - such as server-side image ingestion pipelines - should be sandboxed (e.g., isolated process with restricted memory access) to limit the blast radius of any memory disclosure. End users can eliminate the attack surface entirely by not opening DNG files received from untrusted sources, since exploitation is conditional on user interaction.

Share

CVE-2026-47927 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy