CVE-2026-21337
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 access 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 · moderate confidenceSubstance3D Designer versions 15.1.0 and earlier contain an out-of-bounds read vulnerability in file parsing logic. When a victim opens a specially crafted malicious file, the application reads memory beyond allocated buffers, potentially exposing sensitive data from the application's 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 the Adobe Substance 3D Designer installationCheck the program's executable location, typically in Program Files/Adobe/Adobe Substance 3D Designer, or verify via the Creative Cloud desktop applicationAffected if The application is installed on the system
-
Identify the installed version numberOpen Adobe Substance 3D Designer and navigate to Help > About, or right-click the executable file and select Properties > Details to view the Product VersionAffected if Unable to determine the version number
-
Compare your version against the fixed releaseNote the full version number (for example, 15.1.0, 15.1.1, 15.1.2) and compare it to 15.1.2Affected if The installed version is earlier than 15.1.2 (for example, 15.1.0 or 15.1.1)
-
Assess file opening behaviorDetermine whether the application is used to open external files, particularly from untrusted or unknown sourcesAffected if Users routinely open files in Substance 3D Designer
You are affected if Adobe Substance 3D Designer is installed with a version earlier than 15.1.2 and the application is used to open external 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 files from untrusted sources until Adobe releases an official patch. Apply vendor security updates as soon as they become available.
15.1.2
- Navigate to the Adobe Substance 3D Designer download page or open Adobe Creative Cloud desktop application
- Locate Substance 3D Designer in your installed applications
- Check the current version number to confirm it is below 15.1.2
- Update the application through the Creative Cloud desktop app or download the latest version from Adobe's website
- Restart the application after the update completes
- Verify the updated version is 15.1.2 or later
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-21337 — 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-21337 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