dbcve.org
Substance 3d ViewerApplication · Adobe

CVE-2025-43583

MEDIUM · 5.5 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 0.25 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
Substance3D - Viewer versions 0.22 and earlier are affected by a NULL Pointer Dereference vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability to crash the application, causing disruption in service. 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

A NULL pointer dereference vulnerability exists in Adobe Substance3D Viewer versions 0.22 and earlier. When a user opens a specially crafted malicious file, the application attempts to dereference a NULL pointer during file parsing, causing the application to crash and resulting in denial of service.

MitigationUsers should avoid opening untrusted or unexpected 3D files in Substance3D Viewer until Adobe releases an official patch. Organizations may consider implementing network-based file filtering or user awareness to reduce exposure to malicious files.

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
Substance 3d ViewerApplication
Affected:< 0.25

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. Check if Adobe Substance3D Viewer is installed
    On Windows, open Programs and Features or check C:\Program Files\Adobe\Adobe Substance 3D Viewer. On macOS, check /Applications for Adobe Substance 3D Viewer.app. On Linux, check common application directories.
    Affected if The application is found on the system
  2. Locate the installed version number
    Right-click the application executable and select Properties, then view the Details tab. Alternatively, launch the application and go to Help > About Adobe Substance 3D Viewer.
    Affected if Version information is accessible and can be read
  3. Compare version against the affected range
    The CVE states versions 0.22 and earlier are affected, and all versions below 0.25 are listed as vulnerable. Compare your installed version number (for example, 0.20, 0.21, 0.22) against this threshold.
    Affected if Installed version is 0.22 or earlier, or any version below 0.25

If Adobe Substance3D Viewer is installed and the version is less than 0.25, the environment falls within the affected version range and is vulnerable to this CVE.

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 0.25 or later
Fixed in 0.25
Interim mitigation

Users should avoid opening untrusted or unexpected 3D files in Substance3D Viewer until Adobe releases an official patch. Organizations may consider implementing network-based file filtering or user awareness to reduce exposure to malicious files.

Recommended fix High confidence

version 0.25 or later

  1. Check the current version of Substance 3D Viewer by opening the application and navigating to Help > About, or checking in the application settings
  2. Close any running instances of Substance 3D Viewer
  3. Uninstall the current version of Substance 3D Viewer from the system using the standard uninstallation process for your operating system
  4. Download Substance 3D Viewer version 0.25 or later from the official Adobe website (helpx.adobe.com) or the Adobe Creative Cloud desktop application
  5. Install the downloaded version 0.25 or later
  6. Launch the application and verify the version number matches 0.25 or higher

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

Fix this in Substance 3d Viewer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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