dbcve.org
Dng Software Development KitApplication · Adobe

CVE-2026-47927

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-16
Fix available
A fix is available. Upgrade to 1.7.1.2611 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The DNG SDK versions 1.7.1 2536 and earlier contain an out-of-bounds read vulnerability that allows disclosure of sensitive memory contents. An attacker can exploit this by crafting a malicious DNG file that, when opened by a victim, causes the SDK to read beyond allocated memory boundaries, potentially exposing sensitive data from the application's memory space.

MitigationUpdate the DNG SDK to a patched version beyond 1.7.1 2536. Until patched, exercise caution when opening DNG files from untrusted sources and implement file sanitization or sandboxing for raw image processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dng Software Development KitApplication
Affected:< 1.7.1.2611

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify DNG SDK usage
    Search your system for files named 'dng_sdk.lib', 'dng_sdk.dll', 'libdng_sdk.a', or directories containing 'dng' in the name. Also check your project's dependency list or package manager for 'dng_sdk' references.
    Affected if The DNG SDK library or its development files are present in your environment.
  2. Determine installed SDK version
    Locate the DNG SDK library or header file and inspect its version metadata. In Windows DLLs, right-click the file, select Properties, then Details to view File Version. For static libraries or source distributions, check the version string in the main header file (typically dng_sdk.h) or release notes.
    Affected if The version number shown is 1.7.1.2611 or lower, or if no version is displayed and the SDK appears to be from an older release.
  3. Verify DNG file processing capability
    Review your application or workflow to confirm whether it has functionality to open, parse, render, or convert DNG image files. Check configuration files, file type associations, or processing pipelines for '.dng' extensions.
    Affected if Your system or application processes DNG files in any way (opening, viewing, converting, or thumbnails).
  4. Assess source of DNG files
    Examine where DNG files originate in your workflow. Check if files come from external sources, untrusted users, internet downloads, email attachments, or third-party photographers.
    Affected if DNG files from untrusted or external sources are processed without additional validation.

Your environment is affected if the DNG SDK version is below 1.7.1.2611 and your system processes DNG files, especially from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.7.1.2611 or later
Fixed in 1.7.1.2611
Interim mitigation

Update the DNG SDK to a patched version beyond 1.7.1 2536. Until patched, exercise caution when opening DNG files from untrusted sources and implement file sanitization or sandboxing for raw image processing.

Recommended fix High confidence

DNG SDK version 1.7.1.2611

  1. Identify all applications and systems using the DNG Software Development Kit
  2. Locate the DNG SDK library files (typically named dng_sdk.lib, dng_sdk.dll, or similar) in your project dependencies
  3. Download DNG SDK version 1.7.1.2611 or later from the official Adobe DNG SDK download page at helpx.adobe.com
  4. Replace the older DNG SDK files in your project with the updated version 1.7.1.2611
  5. Rebuild your application or project to incorporate the new SDK files
  6. Test the application to ensure DNG image processing functionality works correctly after the upgrade
  7. Verify that the vulnerable code paths are no longer present in the updated SDK
Caveat Review the Adobe SDK release notes for any API changes between your current version and 1.7.1.2611 that may require code adjustments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dng Software Development Kit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47927 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47927 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data