Substance 3d ModelerApplication · Adobe

CVE-2025-21170

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 1.21.0 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 - Modeler versions 1.15.0 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 · moderate confidence

A NULL pointer dereference vulnerability exists in Substance3D Modeler versions 1.15.0 and earlier when parsing maliciously crafted files. An attacker can trigger this vulnerability by enticing a user to open a specially crafted file, causing the application to crash due to dereferencing a NULL pointer, resulting in denial of service.

MitigationUpgrade Substance3D Modeler to a version newer than 1.15.0 once the vendor releases a patch. Avoid opening untrusted or unexpected 3D model files from unverified sources until the patch is applied.

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 ModelerApplication
Affected:< 1.21.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
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. Determine installed Adobe Substance 3D Modeler version
    Open the application and navigate to Help > About Adobe Substance 3D Modeler, or check the version displayed in the application window title bar
    Affected if The displayed version number is less than 1.21.0 (for example, 1.15.0, 1.10.0, 1.5.0, etc.)
  2. Verify application version via system installed programs list
    On Windows, open Programs and Features or run 'wmic product get name,version'; on macOS, check /Applications folder or run 'mdls' on the .app bundle
    Affected if The listed version is any build earlier than 1.21.0
  3. Confirm the application can open external 3D model files
    Verify that the software has file import functionality enabled and is configured to accept user-provided model files (default behavior)
    Affected if The file import feature is accessible to the user, which is the default configuration for this application

A user is affected if their installed Adobe Substance 3D Modeler version is any release prior to version 1.21.0 and they can open external 3D model files, as both conditions are required for the NULL pointer dereference to be triggered.

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.21.0 or later
Fixed in 1.21.0
Interim mitigation

Upgrade Substance3D Modeler to a version newer than 1.15.0 once the vendor releases a patch. Avoid opening untrusted or unexpected 3D model files from unverified sources until the patch is applied.

Recommended fix High confidence

1.21.0 or later

  1. 1. Close Adobe Substance 3D Modeler if it is currently running
  2. 2. Open Adobe Creative Cloud desktop application or navigate to the Adobe Substance 3D Modeler download page
  3. 3. Check for available updates to Substance 3D Modeler
  4. 4. Download and install version 1.21.0 or later
  5. 5. Verify the installed version by opening the application and checking Help > About Adobe Substance 3D Modeler

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

Fix this in Substance 3d Modeler Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-21170 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