dbcve.org
Dng Software Development KitApplication · Adobe

CVE-2026-47963

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 · high confidence

DNG SDK versions 1.7.1 2536 and earlier contain an out-of-bounds read vulnerability that allows disclosure of sensitive memory contents when a victim opens a specially crafted malicious DNG file.

MitigationAvoid opening untrusted or unverified DNG files; apply vendor patches to the DNG SDK once released and rebuild any applications that integrate the affected SDK version.

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 applications using the DNG SDK
    Review your installed software for applications that process DNG (Digital Negative) image files, such as Adobe products, Lightroom, Camera RAW plugins, or custom applications that handle DNG conversion or processing
    Affected if Any application that processes DNG files is present and uses the affected SDK version
  2. Locate the DNG SDK library file
    Search for 'dng_sdk.dll' (Windows), 'libdng_sdk.so' (Linux), or 'dng_sdk.framework' (macOS) in application directories or system libraries; also check application bundle contents or dependency directories
    Affected if The DNG SDK library file exists on the system
  3. Determine the installed DNG SDK version
    Right-click the SDK library file and select Properties > Details to view the File Version, or use a command like 'strings dng_sdk.dll | grep -i version' or examine the resource metadata; for linked SDKs, check the application's dependency manifest or build configuration
    Affected if The version number is 1.7.1.2536 or earlier, or any version below 1.7.1.2611
  4. Confirm the vulnerable code path is reachable
    Verify that the application can open and parse DNG files; the vulnerability triggers when processing a specially crafted malicious DNG file, so any application that opens DNG files without strict validation is potentially exposed
    Affected if The application processes DNG files as input without additional sandboxing or validation layers

The environment is affected if any application or library on the system contains Adobe DNG SDK version 1.7.1.2536 or earlier (anything below 1.7.1.2611) and that SDK is used to process DNG image files.

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

Avoid opening untrusted or unverified DNG files; apply vendor patches to the DNG SDK once released and rebuild any applications that integrate the affected SDK version.

Recommended fix High confidence

1.7.1.2611 or later

  1. Identify all applications or projects using the DNG Software Development Kit
  2. Determine the current version of DNG SDK in use (vulnerable if version < 1.7.1.2611)
  3. Navigate to Adobe's official helpx.adobe.com to obtain the fixed DNG SDK version 1.7.1.2611 or later
  4. Download the updated DNG SDK package from Adobe's official source
  5. Replace the vulnerable SDK files in your project with the fixed version 1.7.1.2611
  6. Rebuild and recompile any applications that depend on the DNG SDK
  7. Verify the new version is correctly installed (confirm version 1.7.1.2611 or higher is in use)
  8. Test applications to ensure functionality remains intact after the update

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47963 — 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-47963 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