CVE-2026-21335
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 · high confidenceAn out-of-bounds write vulnerability in Substance3D Designer versions 15.1.0 and earlier allows arbitrary code execution when a user opens a maliciously crafted file. The vulnerability occurs during file parsing where improper bounds checking leads to memory corruption.
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.
-
Check if Adobe Substance 3D Designer is installedSearch for the application on the system. On Windows, check Program Files/Adobe/Adobe Substance 3D Designer or use system inventory/software listing tools. On macOS, check /Applications or use system profiling tools.Affected if The software is present on the system
-
Identify the installed version numberOpen Adobe Substance 3D Designer and navigate to Help > About Adobe Substance 3D Designer to view the exact version, or query the installed software through system administration tools that report version information.Affected if The installed version is 15.1.0 or any version lower than 15.1.2
-
Confirm file handling capability existsVerify the application can open or parse its native file formats (.sbsar, .sbs files). This is the standard functionality that triggers the vulnerable code path during file parsing.Affected if The application can open or parse files (this is the standard use case and required for the vulnerability to be triggered)
A system is affected if Adobe Substance 3D Designer version 15.1.0 or any version below 15.1.2 is installed and users have the ability to open files, since the vulnerability is triggered during file parsing of maliciously crafted 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 · scoped15.1.2
Users should avoid opening untrusted or unexpected files in Substance3D Designer until a vendor patch is released. Organizations should implement file handling policies and consider sandboxing for untrusted content.
Substance 3D Designer 15.1.2
- Close any running instances of Substance 3D Designer
- Navigate to the official Adobe website and download Substance 3D Designer version 15.1.2 or later
- Run the downloaded installer and follow the on-screen prompts to complete the upgrade
- After installation, launch Substance 3D Designer and verify the version is 15.1.2 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21335 — 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-21335 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