CVE-2026-34675
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 - Painter versions 12.0.2 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 Painter versions 12.0.2 and earlier contain an out-of-bounds write vulnerability that allows arbitrary code execution in the context of the current user. The attack requires victim interaction—specifically opening a malicious file—to trigger the vulnerability.
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< 12.0.3CVSS 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.
-
Locate Adobe Substance 3D Painter installationCheck for the application in typical installation directories: Windows typically installs to C:\Program Files\Adobe\Adobe Substance 3D Painter or C:\Program Files (x86)\Adobe\Adobe Substance 3D Painter. On macOS, check /Applications for Adobe Substance 3D Painter.appAffected if The application is found installed on the system
-
Determine the installed version numberOn Windows: Right-click the executable (Substance 3D Painter.exe), select Properties, and view the Details tab for Product Version. On macOS: Right-click Adobe Substance 3D Painter.app, select Get Info, and view the Version field under GeneralAffected if The version displayed is 12.0.2 or earlier, or shows a version < 12.0.3
-
Check Windows Registry for versionOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\, look for an entry named Adobe Substance 3D Painter and view the DisplayVersion valueAffected if The DisplayVersion value shows 12.0.2 or earlier, or a version less than 12.0.3
-
Verify the application's file open functionality is accessibleLaunch the application normally to confirm it is functional and can open files. The vulnerability is triggered when opening malicious files, so if the application can be run and accepts file input, the attack surface existsAffected if The application launches successfully and can be used to open external files
The system is affected if Adobe Substance 3D Painter is installed and the installed version is 12.0.2 or earlier (any version below 12.0.3).
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 · scoped12.0.3
Update Substance3D Painter to a version newer than 12.0.2 once available. Avoid opening files from untrusted sources and ensure endpoint protection is active.
12.0.3
- 1. Close any running instances of Adobe Substance 3D Painter
- 2. Back up your current project files and custom presets if desired
- 3. Open Adobe Creative Cloud desktop application or navigate to helpx.adobe.com
- 4. Locate Adobe Substance 3D Painter in your installed applications
- 5. Click the Update button next to Substance 3D Painter to install version 12.0.3 or later
- 6. Wait for the update to download and install completely
- 7. Verify the installed version by opening Substance 3D Painter and checking Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34675 — 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-34675 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