CVE-2026-21305
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 11.0.3 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 confidenceAn out-of-bounds write vulnerability exists in Substance3D Painter versions 11.0.3 and earlier when parsing maliciously crafted files, allowing arbitrary code execution in the context of the current user. The vulnerability requires user interaction where a victim must open a specially crafted malicious file.
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< 11.1.2CVSS 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.
-
Identify if Adobe Substance 3D Painter is installedOn Windows, check for the application in Program Files/Adobe or use Add/Remove Programs. On macOS, check /Applications for Adobe Substance 3D Painter.appAffected if The application is present on the system
-
Determine the installed version numberOn Windows, right-click the executable (Substance 3D Painter.exe) and select Properties > Details to view the File Version. On macOS, right-click the app bundle, select Get Info, and check the Version field under Adobe Substance 3D PainterAffected if The displayed version is 11.0.3 or earlier, or any version below 11.1.2
-
Confirm the specific vulnerable versionCompare the installed version string against the affected range: any version less than 11.1.2 (including 11.1.1, 11.1.0, 11.0.3, 11.0.2, 11.0.1, 11.0.0, and earlier releases) is vulnerableAffected if The version number is below 11.1.2
-
Verify the attack vector requires user interactionThe vulnerability is triggered only when the application opens a specially crafted malicious file. Check whether the application has file association handlers configured or if users commonly import files from external sourcesAffected if Users can open or import files within the application, making the exploit reachable through social engineering
The environment is affected if Adobe Substance 3D Painter is installed with any version below 11.1.2 and the application can be used to open files from untrusted sources.
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 · scoped11.1.2
Update Substance3D Painter to a version newer than 11.0.3 when the patch becomes available. Avoid opening untrusted or unknown files in the application until the update is applied.
Substance 3D Painter 11.1.2 or later
- Navigate to the Adobe Creative Cloud desktop application or the Substance 3D Painter download page
- Locate Substance 3D Painter in your installed applications
- Check for updates or download version 11.1.2 or later
- Install the updated version of Substance 3D Painter
- Verify the installed version by opening the application and checking Help > About (or similar)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21305 — 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-21305 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