CVE-2026-21300
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 file parsing logic. When the application opens a specially crafted malicious file, it attempts to dereference a NULL pointer, causing the application to crash and resulting in denial-of-service.
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.
-
Locate Adobe Substance3D Modeler installationSearch for the application installation directory. Common paths include C:\Program Files\Adobe\Adobe Substance 3D Modeler on Windows or /Applications/Adobe Substance 3D Modeler on macOS. Use system inventory tools or check Add/Remove Programs list.Affected if The application is installed on the system
-
Identify installed version numberNavigate to the application installation folder and locate the version information. On Windows, right-click the executable file (Adobe Substance 3D Modeler.exe), select Properties, and view the Details tab for Product Version. On macOS, right-click the application bundle, select Get Info, and check the Version field.Affected if A version number is displayed in the file properties
-
Compare version against affected rangeTake the installed version number identified in the previous step and compare it to the affected version range: any version lower than 1.22.5 is vulnerable. Note that version 1.22.4 and all earlier versions are affected.Affected if Installed version is 1.22.4 or earlier, or any version below 1.22.5
The environment is affected if Adobe Substance3D Modeler is installed with a version lower than 1.22.5, as the NULL pointer dereference vulnerability triggers when the application opens specially crafted malicious files.
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
Update Substance3D Modeler to a version newer than 1.22.4 when a patch becomes available. Avoid opening files from untrusted sources.
1.22.5
- Close Adobe Substance 3D Modeler if it is currently running
- Open Adobe Creative Cloud desktop application or navigate to the Adobe Substance 3D Modeler download page at helpx.adobe.com
- Check for available updates or download version 1.22.5 specifically
- Run the installer and follow the on-screen prompts to complete the upgrade
- After installation completes, launch Substance 3D Modeler to verify the upgrade was successful
- Verify the installed version is 1.22.5 or later by checking the application about/help section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21300 — 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-21300 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