CVE-2025-21167
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 14.1 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 14.1 and earlier contain an out-of-bounds read vulnerability. When a user opens a specially crafted malicious file, the application reads memory beyond allocated buffer boundaries, potentially exposing sensitive memory contents. This information disclosure can be leveraged to defeat ASLR as a secondary attack objective.
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< 14.1.1CVSS 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.
-
Identify installed Adobe Substance 3D Designer versionOpen the application, then go to Help > About Adobe Substance 3D Designer to display the version number. Alternatively, check Add or Remove Programs (Windows) or the Applications folder (macOS) for the installed version.Affected if The displayed version is earlier than 14.1.1 (for example, 14.1, 14.0, or any earlier release).
-
Confirm Windows registry version entry (Windows only)Open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Adobe Substance 3D Designer} or search for keys containing 'Substance 3D Designer' under the Uninstall registry hive. Read the DisplayVersion value.Affected if The registry DisplayVersion value shows a version number lower than 14.1.1.
-
Verify file opening behavior is possibleConfirm that the application can open files from external sources. This is the default behavior for Substance 3D Designer as a file-based design tool.Affected if The application can open .sbsar or .sbs files, which is the default state. No special configuration is required for the vulnerability to trigger.
A system is affected if Adobe Substance 3D Designer version 14.1.1 or later is NOT installed, since the vulnerability exists in any version prior to 14.1.1 and triggers when opening a specially crafted malicious file.
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 · scoped14.1.1
Users should avoid opening files from untrusted sources until Adobe releases an official patch. Organizations may consider implementing file sandboxing or endpoint protection that scans files before they are opened in Designer.
14.1.1
- Back up any custom packages, graphs, or user settings from your current installation
- Navigate to the official Adobe support page at helpx.adobe.com
- Locate and download Substance 3D Designer version 14.1.1 or later
- Uninstall the current version of Substance 3D Designer from your system
- Install the downloaded version 14.1.1
- Launch the application and verify it runs without errors
- Test that existing projects open correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21167 — 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-2025-21167 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