CVE-2026-21334
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 - Designer versions 15.1.0 and earlier are affected by an out-of-bounds write vulnerability that could result in arbitrary code execution in the context of the current user. 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 confidenceSubstance3D Designer versions 15.1.0 and earlier contain an out-of-bounds write vulnerability that can be triggered by opening a malicious file, leading to arbitrary code execution in the context of the current user.
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< 15.1.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 the installed Adobe Substance 3D Designer executableNavigate to the installation directory (commonly C:\Program Files\Adobe\Adobe Substance 3D Designer or C:\Program Files (x86)\Adobe\Adobe Substance 3D Designer) and locate the main executable file (Substance 3D Designer.exe).Affected if The executable exists and the software is installed on the system.
-
Check the installed software versionRight-click on the Substance 3D Designer.exe file, select Properties, and view the Details tab to see the Product Version or File Version field.Affected if The version displayed is 15.1.0 or earlier, or shows a version less than 15.1.2.
-
Alternatively, check version from application menuLaunch Adobe Substance 3D Designer and navigate to Help > About Adobe Substance 3D Designer to view the exact version number displayed in the dialog.Affected if The version shown is 15.1.0 or earlier, or shows a version less than 15.1.2.
-
Check Windows Registry for version informationOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or HKEY_CLASSES_ROOT\Applications\, looking for an entry related to Adobe Substance 3D Designer. The DisplayVersion value indicates the installed version.Affected if The DisplayVersion value shows a version less than 15.1.2.
The system is affected if Adobe Substance 3D Designer is installed and the installed version is earlier than 15.1.2 (such as 15.1.0 or any earlier version).
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 · scoped15.1.2
Users should refrain from opening untrusted or unsolicited files and update to a patched version of Substance3D Designer once released by Adobe.
15.1.2 or later
- 1. Back up any important projects and custom nodes from your current Adobe Substance 3D Designer installation
- 2. Navigate to the official Adobe download page at helpx.adobe.com
- 3. Locate and download Adobe Substance 3D Designer version 15.1.2 or later
- 4. Close any running instances of Substance 3D Designer
- 5. Run the installer and follow the on-screen prompts to complete the upgrade
- 6. After installation, verify the version by opening Designer and checking Help > About Adobe Substance 3D Designer
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21334 — 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-21334 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