DNG SDK versions 1.7.1 2410 and earlier are affected by an out-of-bounds read vulnerability that could lead to memory exposure. An attacker could leverage this vulnerability to disclose sensitive information stored in memory. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
Security readout for executives and security teams
Plain-English summary
A malicious DNG file can cause affected Adobe DNG SDK versions to read beyond intended memory boundaries, potentially exposing sensitive information. A victim must open the file, limiting opportunistic remote attacks but leaving file-processing workflows and users exposed.
Executive priority
Prioritize affected creative, imaging, and file-processing environments that handle external files. Treat this as a timely confidentiality remediation, not an emergency, unless sensitive-memory exposure or high-risk file intake materially increases business impact.
Technical view
CVE-2026-21355 is a CWE-125 out-of-bounds read with CVSS 3.1 score 5.5. It requires local delivery and user interaction, needs no privileges, and affects confidentiality without documented integrity or availability impact.
Likely exposure
Exposure is most likely where affected DNG SDK code is deployed or integrated and users can open untrusted DNG files. The bundle contains conflicting version boundaries, so organizations should confirm applicability against Adobe's advisory.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires a victim to open a malicious file. No exploit method or observed campaign is documented here.
Researcher notes
The bundle is internally inconsistent: its description says 1.7.1 2410 and earlier, while affected metadata includes 1.7.1.2471 and defaults other versions to unaffected. Confirm the exact boundary with Adobe before making exposure decisions. No technical proof, patch version, or exploitation evidence is supplied.
Mitigation direction
Inventory applications and workflows incorporating the Adobe DNG SDK.
Follow Adobe's advisory to identify and install the corrected SDK release.
Limit opening or processing of untrusted DNG files until remediation is confirmed.
Warn users and file-processing teams about unexpected or unsolicited DNG files.
Validation and detection
Check dependency manifests, build records, and packaged components for the DNG SDK version.
Reconcile discovered versions with Adobe's authoritative affected-version guidance.
Confirm rebuilt or updated applications no longer contain the vulnerable SDK version.
Verify controls restrict untrusted DNG ingestion where immediate updating is unavailable.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.