dbcve.org
Dng Software Development KitApplication · Adobe

CVE-2025-64784

HIGH · 7.1 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to after 1.7.0 or later.
See remediation →
74/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.0 and earlier are affected by a Heap-based Buffer Overflow vulnerability that could lead to memory exposure or application denial of service. An attacker could leverage this vulnerability to disclose sensitive memory 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 (Digital Negative SDK) versions 1.7.0 and earlier contain a heap-based buffer overflow vulnerability that can be triggered when processing a specially crafted malicious DNG image file. Successful exploitation can lead to memory information disclosure or application denial of service.

MitigationUsers should avoid opening untrusted or suspicious DNG files. Organizations should update the DNG SDK to a version beyond 1.7.0 once a patch is released, and scan existing DNG processing pipelines for usage of the affected SDK versions.

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.0

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
High

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

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. Locate DNG SDK libraries in your environment
    Search for files named 'dng_sdk.lib', 'dng.dll', 'libdng.a', or similar DNG SDK binary files on your system. Check common installation directories such as /usr/lib, /usr/local/lib, Windows\System32, or application-specific lib folders.
    Affected if DNG SDK library files are found and their version is 1.7.0 or earlier (compare your found version against the affected range)
  2. Identify applications using the DNG SDK
    Search your codebase or application binaries for references to 'dng' namespace, 'DNG SDK', or 'AdobeDNG' strings. Review software dependency manifests (like .deps, package.json, requirements.txt) or linker inputs that include DNG SDK.
    Affected if An application or service links against or embeds the DNG SDK and processes DNG image files from external or untrusted sources
  3. Determine DNG processing data flow
    Inspect configuration files, application logs, or code that shows how DNG files enter your system. Look for file upload handlers, image processing pipelines, or thumbnail generation services that accept DNG input.
    Affected if Your system accepts DNG files from users, external APIs, or untrusted sources and passes them to DNG SDK functions for processing
  4. Check installed SDK version via metadata
    If the SDK was installed via a package manager (npm, pip, nuget, brew), run 'npm list dng-sdk', 'pip show dng-sdk', or equivalent to query the installed version. Check any version.h, version.cpp, or README files distributed with the SDK.
    Affected if The reported version number is 1.7.0 or lower, indicating the vulnerable version is in use
  5. Audit DNG file processing endpoints
    Review web application endpoints, CLI tools, or background jobs that handle DNG image uploads or batch processing. Verify whether the DNG SDK is invoked without prior validation or sanitization of the input file.
    Affected if DNG files from external or untrusted sources are processed directly by the DNG SDK without sandboxing or content scanning

You are affected if your environment contains a version of the Adobe DNG SDK at 1.7.0 or earlier that processes DNG image files from untrusted or external 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 a release after 1.7.0
Interim mitigation

Users should avoid opening untrusted or suspicious DNG files. Organizations should update the DNG SDK to a version beyond 1.7.0 once a patch is released, and scan existing DNG processing pipelines for usage of the affected SDK versions.

Recommended fix Moderate confidence

Latest available DNG SDK version (greater than 1.7.0)

  1. 1. Navigate to the Adobe DNG SDK download page on helpx.adobe.com
  2. 2. Locate the most recent version of the DNG SDK (verify version number is greater than 1.7.0)
  3. 3. Download the updated DNG SDK package for your platform
  4. 4. Replace older DNG SDK files in your project with the new version
  5. 5. Rebuild and test your application to ensure the SDK functions correctly
Caveat Review Adobe's release notes for any API changes between your current version and the new version

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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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