CVE-2026-34664
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 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could lead to arbitrary file system read. An attacker could exploit this vulnerability to access sensitive files and directories outside the intended access scope. Exploitation of this issue requires user interaction in that a victim must open a malicious file. Scope is changed.
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 a path traversal vulnerability in its file loading mechanism. When a victim opens a maliciously crafted file, the application fails to properly validate file paths, allowing the attacker to read arbitrary files outside the intended directory scope. The 'scope changed' designation indicates the vulnerability allows the application to access resources beyond its normal authorization boundaries.
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.0CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/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 Adobe Substance 3D Designer, then go to Help > About Adobe Substance 3D Designer to view the exact version number displayed in the dialog windowAffected if The version shown is 15.1.0 or any version number lower than 15.1.0
-
Check application executable version via file propertiesNavigate to the installation directory (typically C:\Program Files\Adobe\Adobe Substance 3D Designer), right-click on Substance 3D Designer.exe, select Properties, and view the File version under the Details tabAffected if The file version listed is 15.1.0.x or lower
-
Verify Windows registry version entryOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Substance 3D Designer (or HKEY_CURRENT_USER\SOFTWARE\Adobe\Substance 3D Designer on per-user installs), and check the Version or CurrentVersion valueAffected if The registry version value is 15.1.0 or lower
-
Determine if file loading from external sources is possibleCheck whether the application can open files from user-controlled locations - attempt to open a test file stored in a user folder (Documents or Downloads) using File > OpenAffected if The application successfully loads files from arbitrary filesystem locations, indicating the file loading feature is active and accessible
A defender is affected if Adobe Substance 3D Designer version 15.1.0 or lower is installed, since the path traversal vulnerability exists in the file loading mechanism for all such versions.
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.
From vendor dataApply the vendor patch (update to a version newer than 15.1.0 once available) and avoid opening files from untrusted sources until the patch is applied. Organizations should also implement file handling controls and user awareness training about the risks of opening untrusted design files.
- Consultation2.0 h
- Implementation8.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34664 — 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-34664 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