CVE-2026-34682
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 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 · high confidenceSubstance3D Designer versions 15.1.0 and earlier contain an out-of-bounds write vulnerability that can be triggered by opening a maliciously crafted file, leading to arbitrary code execution in the context 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<= 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
- 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 the system for the presence of Adobe Substance 3D Designer. On Windows, this is typically found in Program Files or Program Files (x86). On macOS, check the Applications folder. You can also check the Windows Registry under HKLM\SOFTWARE\Adobe\Substance3DDesigner or use system inventory tools.Affected if Adobe Substance 3D Designer is found installed on the system
-
Determine the installed versionLocate the version information for the installed Adobe Substance 3D Designer. On Windows, right-click the executable, select Properties, and check the Details tab for File Version. On macOS, right-click the app, select Get Info, and check the Version field. Alternatively, check the application's About or Help menu.Affected if A version number of 15.1.0 or earlier is identified
-
Compare against affected version rangeCompare the identified version number against the affected version range. The affected versions are 15.1.0 and any version released before it.Affected if The installed version is 15.1.0 or earlier (for example, 15.0.x, 14.x.x, or older)
-
Confirm the file handling vectorThe vulnerability is triggered when opening a maliciously crafted design file. Identify whether the user routinely opens design files (.sbsar, .sbs, or other Substance file formats) from untrusted or unknown sources.Affected if Users open design files from untrusted sources without validation
If Adobe Substance 3D Designer version 15.1.0 or earlier is installed and users open design files from untrusted sources, the environment is affected by CVE-2026-34682.
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 dataUpgrade Substance3D Designer to a version newer than 15.1.0 when a patch is released by Adobe, and exercise caution when opening design files from untrusted sources.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34682 — 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-34682 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