CVE-2026-21340
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 read vulnerability that could lead to memory exposure. An attacker could leverage this vulnerability to disclose sensitive information stored in memory. 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 confidenceSubstance3D Designer versions 15.1.0 and earlier contain an out-of-bounds read vulnerability. When a victim opens a specially crafted malicious file, the application reads beyond allocated memory boundaries, potentially exposing sensitive data from the process memory space.
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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 Substance3D Designer installationCheck common installation paths: Windows: C:\Program Files\Adobe\Adobe Substance 3D Designer\ or C:\Program Files (x86)\Adobe\Adobe Substance 3D Designer\. On macOS: /Applications/Adobe Substance 3D Designer/. On Windows, also check registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Substance 3D DesignerAffected if Application directory or registry key exists indicating the product is installed
-
Determine installed version numberOpen the application and navigate to Help > About Adobe Substance 3D Designer to view the exact version. On Windows, version may also be visible in the registry or in the executable properties (right-click on the .exe file and select Properties > Details)Affected if Version displayed is 15.1.0 or any version earlier than 15.1.2
-
Confirm vulnerability applicabilityThe vulnerability triggers when opening specially crafted malicious files. Check if the user routinely opens .sbsar, .sbs, or other Substance files from untrusted sourcesAffected if User opens files from untrusted or unknown sources in the affected application version
User is affected if Adobe Substance 3D Designer version is 15.1.0 or earlier (less than 15.1.2) and they open files in the application
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
Update Substance3D Designer to a version newer than 15.1.0 when a patch becomes available. Additionally, avoid opening files from untrusted or unknown sources.
15.1.2 or later
- 1. Ensure you have a backup of your current projects and settings
- 2. Open Adobe Creative Cloud desktop application or navigate to the Substance 3D Designer download page
- 3. Locate Substance 3D Designer in the available applications
- 4. Check if version 15.1.2 or later is available for download
- 5. Download and install version 15.1.2 or the latest available version
- 6. After installation, verify the installed version by opening Substance 3D Designer and checking the version number in the application menu
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21340 — 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-21340 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