dbcve.org
Dng Software Development KitApplication · Adobe

CVE-2026-48267

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

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 a NULL Pointer Dereference vulnerability that could result in an application denial-of-service. An attacker could exploit this vulnerability to crash the application, leading to a denial-of-service condition. 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 a NULL pointer dereference vulnerability when parsing maliciously crafted DNG (Digital Negative) image files. The vulnerability triggers during file processing when the code attempts to dereference a NULL pointer, causing the application to crash and result in a denial-of-service condition.

MitigationAvoid opening untrusted or unknown DNG files. Apply vendor patches when available to address the NULL pointer dereference in the SDK's file parsing routines.

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
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 checks

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

  1. Locate the DNG SDK installation
    Search for files named 'dng_sdk', 'dng' with .dll, .so, or .a extensions, or check application installation directories for Adobe DNG SDK components. Look in common library paths like /usr/lib, /Library/Frameworks, or application-specific folders.
    Affected if The DNG SDK library files are found on the system.
  2. Identify the installed DNG SDK version
    Check version metadata in SDK files, DLL properties, or associated version files. Look for version strings like '1.7.1' or build numbers such as '2536' in file properties, manifest files, or embedded version info.
    Affected if The version number is visible and can be compared against the affected range.
  3. Compare version against affected range
    Determine if the installed version is < 1.7.1.2611. Versions 2536 and earlier are explicitly listed as vulnerable. Any version before 1.7.1.2611 should be considered at risk.
    Affected if The installed version is 1.7.1.2536 or earlier, or any version below 1.7.1.2611.
  4. Check if DNG file processing is enabled
    Identify applications or services that use the DNG SDK for parsing image files. Look for configurations enabling DNG format support, or audit running processes that handle Digital Negative image files.
    Affected if Applications or services are configured to process DNG files using the vulnerable SDK.

The environment is affected if the DNG SDK version is below 1.7.1.2611 and applications are parsing DNG image files with the vulnerable code path enabled.

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 unknown DNG files. Apply vendor patches when available to address the NULL pointer dereference in the SDK's file parsing routines.

Recommended fix High confidence

DNG Software Development Kit 1.7.1.2611 or later

  1. 1. Identify all applications or tools that use the DNG Software Development SDK.
  2. 2. Determine the current version of DNG SDK in use by checking the library files or project dependencies.
  3. 3. Download DNG SDK version 1.7.1.2611 or a later stable release from the official Adobe source (helpx.adobe.com).
  4. 4. Update the SDK in all affected applications by replacing the old SDK libraries with the new version.
  5. 5. Rebuild and recompile any applications that link against the DNG SDK.
  6. 6. Re-test the applications to ensure proper functionality after the update.
  7. 7. Distribute updated software to end users.
Caveat Review release notes for any API changes or deprecations between your current version and 1.7.1.2611

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,460
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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