dbcve.org
Substance 3d DesignerApplication · Adobe

CVE-2026-21338

MEDIUM · 5.5 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 15.1.2 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 - Designer versions 15.1.0 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 to services. 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

Substance3D Designer versions 15.1.0 and earlier contain a NULL Pointer Dereference vulnerability that can be triggered when a user opens a specially crafted malicious file. The vulnerability causes the application to crash due to attempting to dereference a null pointer, resulting in denial-of-service conditions.

MitigationUsers should avoid opening files from untrusted sources. Organizations should update Substance3D Designer to a version newer than 15.1.0 once the vendor releases a patch, and consider implementing file type restrictions or sandboxing for the application.

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 DesignerApplication
Affected:< 15.1.2

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 installed Adobe Substance 3D Designer version
    Open Adobe Substance 3D Designer, then navigate to Help > About Adobe Substance 3D Designer to view the exact version number displayed in the application window
    Affected if The displayed version is 15.1.0 or earlier, or any version lower than 15.1.2
  2. Verify version via Windows Programs and Features
    Open Windows Control Panel > Programs and Features, locate 'Adobe Substance 3D Designer' in the list, and check the Version column
    Affected if The listed version is 15.1.0 or earlier, or any version lower than 15.1.2
  3. Check application crash logs for null pointer errors
    Navigate to the application log directory (typically %APPDATA%\Adobe\Substance 3D Designer\logs) and review recent log files for entries containing 'null pointer' or access violation errors that occurred when opening files
    Affected if Crash logs show null pointer dereference errors occurring when opening specific files
  4. Review recent file opening activity
    Check the application's recent files list or document timeline to identify if users have been opening files from untrusted or unknown sources
    Affected if Users have opened files from untrusted or unknown origins, especially .sbsar or .sbs files
  5. Inspect application security settings
    In Substance 3D Designer, go to Edit > Preferences > General and check if there are any file handling security options enabled or disabled
    Affected if File validation or security warnings are disabled and users can open files without prompts

A user is affected if Adobe Substance 3D Designer version is 15.1.0 or earlier (lower than 15.1.2) and they open specially crafted malicious files from untrusted 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 15.1.2 or later
Fixed in 15.1.2
Interim mitigation

Users should avoid opening files from untrusted sources. Organizations should update Substance3D Designer to a version newer than 15.1.0 once the vendor releases a patch, and consider implementing file type restrictions or sandboxing for the application.

Recommended fix Moderate confidence

15.1.2 or later

  1. Open Adobe Creative Cloud desktop application or navigate to the Adobe Substance 3D Designer product page
  2. Check for available updates for Substance 3D Designer
  3. If an update to version 15.1.2 or later is available, initiate the update process
  4. Alternatively, download the latest version directly from the Adobe Substance 3D Designer download page at helpx.adobe.com
  5. After installation, verify the version by opening Substance 3D Designer and checking Help > About Adobe Substance 3D Designer

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

Fix this in Substance 3d Designer Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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