CVE-2026-21301
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 · uneditedSubstance3D - Modeler versions 1.22.4 and earlier are affected by a NULL Pointer Dereference vulnerability that could lead to application denial-of-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 confidenceAdobe Substance3D Modeler versions 1.22.4 and earlier contain a NULL Pointer Dereference vulnerability in the file parsing logic. When processing a maliciously crafted file, the application attempts to dereference a null pointer, causing a crash and resulting in denial of service. Successful exploitation requires user interaction—specifically, the victim must open the malicious file.
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.22.5CVSS 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.
-
Identify Adobe Substance3D Modeler installation versionOpen the application, then navigate to Help > About Adobe Substance 3D Modeler to view the installed version number. Alternatively, check the version in the application's installation directory or via Windows Programs and Features.Affected if The displayed version is 1.22.4 or earlier, meaning it is less than 1.22.5
-
Confirm file parsing is the attack vectorThis vulnerability is triggered during the parsing of crafted model files. No specific application setting or feature toggle needs to be enabled; the flaw exists in the core file parsing logic.Affected if The application processes input files, making any user who opens untrusted files potentially affected regardless of settings
A user is affected if Adobe Substance 3D Modeler version 1.22.4 or earlier is installed, and the user opens a maliciously crafted file, leading to a null pointer dereference crash.
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.
dbcve · scoped1.22.5
Avoid opening untrusted or unsolicited files in Substance3D Modeler until an official vendor patch is released. Users should verify file sources before opening them in the application.
1.22.5 or later
- Verify current version of Adobe Substance 3D Modeler by opening the application and checking 'Help' > 'About'
- Download the latest version of Substance 3D Modeler from the official Adobe website or Creative Cloud desktop application
- Close any running instances of Substance 3D Modeler
- Run the installer downloaded in step 2
- Follow the on-screen prompts to complete the installation
- Restart the application after installation completes
- Verify the installed version is 1.22.5 or later via 'Help' > 'About'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21301 — 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-2026-21301 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