CVE-2025-64894
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 · uneditedDNG SDK versions 1.7.0 and earlier are affected by an Integer Overflow or Wraparound vulnerability that could lead to application denial-of-service. An attacker could exploit this issue to cause the application to crash or become unresponsive. 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 confidenceThe DNG SDK versions 1.7.0 and earlier contain an integer overflow vulnerability in its file parsing logic. When processing a maliciously crafted DNG file, the integer overflow can cause memory corruption leading to application crash or unresponsiveness, requiring user interaction (opening the file) to trigger.
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<= 1.7.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate DNG SDK installationSearch the system for files named 'dng' with extensions such as .dll, .so, .lib, .a, .jar, or look for directories containing 'dng' in their name. Check common locations like /usr/lib, /usr/local/lib, project dependencies folders, or application bin directories.Affected if DNG SDK files are present on the system
-
Identify DNG SDK versionInspect the SDK library file metadata (version resource on Windows, version info embedded in binary on Linux/Mac) or check any accompanying version.txt, CHANGELOG, or manifest file in the SDK directory. If the SDK is embedded in an application, check the application's about panel or dependency manifest for the DNG SDK version.Affected if The version returned is 1.7.0 or any version lower than 1.7.0
-
Confirm DNG file parsing is in useReview application logs, configuration files, or code that references DNG handling functionality. Search the codebase or runtime environment for calls to DNG parsing functions (such as dng_parser, ReadDNG, or similar APIs exported by the SDK).Affected if The application or service processes DNG image files as part of its normal operation
-
Verify user-triggered file handlingExamine how the application handles file input. Check if the application exposes functionality where a user can open, import, or load DNG files through file dialogs, drag-and-drop, or file upload mechanisms.Affected if Users can directly open or load DNG files into the application
The environment is affected if the DNG SDK version is 1.7.0 or earlier and the application or service processes DNG files via user-initiated file operations.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate DNG SDK to a version after 1.7.0 when a patch is released; enforce user training to avoid opening untrusted DNG files from unknown sources as a compensating control.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64894 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64894 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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