CVE-2025-21164
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 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 14.1 and earlier contains an out-of-bounds write vulnerability that can be triggered by opening a malicious file, allowing arbitrary code execution with the privileges 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< 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
- 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.
-
Verify Adobe Substance 3D Designer is installedCheck for the application in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look for the program folder in C:\Program Files\Adobe\Adobe Substance 3D DesignerAffected if The application is found on the system
-
Determine installed version numberOpen Adobe Substance 3D Designer and go to Help > About, or check the version in Add/Remove Programs, or run: powershell (Get-Item 'C:\Program Files\Adobe\Adobe Substance 3D Designer\Substance 3D Designer.exe').VersionInfo.ProductVersionAffected if The version shown is 14.1 or earlier, or any version below 14.1.1
-
Confirm version is within vulnerable rangeCompare your installed version to the affected range: versions prior to 14.1.1 are vulnerableAffected if Your installed version is less than 14.1.1
You are affected if Adobe Substance 3D Designer is installed and the version is lower than 14.1.1.
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
Upgrade Substance3D Designer to a version newer than 14.1. Avoid opening untrusted or unexpected files until the update is applied.
14.1.1
- Open Substance 3D Designer and navigate to Help > About Substance 3D Designer to confirm the current installed version
- If the version is earlier than 14.1.1, proceed to the Adobe support portal at helpx.adobe.com or the official Adobe Substance 3D download page
- Download the version 14.1.1 installer for your operating system
- Close any running instances of Substance 3D Designer
- Run the installer and follow the on-screen prompts to complete the installation
- After installation completes, restart Substance 3D Designer and verify the version shows 14.1.1 under Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21164 — 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-21164 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