CVE-2026-27217
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.1.2 and earlier are affected by a NULL Pointer Dereference vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability to crash the application, causing disruption to its availability. 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 confidenceA NULL Pointer Dereference vulnerability exists in Adobe Substance3D Painter versions 11.1.2 and earlier. When a user opens a specially crafted malicious file, the application attempts to dereference a NULL pointer, causing an access violation that crashes the application and results in denial of service.
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.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
-
Check installed Adobe Substance3D Painter versionOpen the application and go to Help > About Adobe Substance 3D Painter, or check the version in your system's installed programs list (Windows: Programs and Features, macOS: Applications folder Get Info)Affected if The version displayed is 11.1.2 or earlier
-
Confirm version via application launcher or installerIf you use Adobe Creative Cloud desktop app, check the installed apps section for Substance3D Painter version; alternatively check any installer logs or the original installer package you usedAffected if The recorded version is below 11.1.3
-
Assess file opening exposureIdentify whether you open Substance files (.sbsar, .sbs, or associated asset files) from external or untrusted sources - this is the trigger condition for the NULL pointer dereferenceAffected if You open files from untrusted or unknown sources using the vulnerable version
You are affected if your installed Adobe Substance3D Painter version is 11.1.2 or earlier and you open files from untrusted or unknown sources, as the vulnerability triggers upon opening a specially crafted malicious file.
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.3
Update Substance3D Painter to a version newer than 11.1.2 when a patch becomes available. Avoid opening files from untrusted or unknown sources until the update is applied.
11.1.3
- 1. Launch Substance 3D Painter and navigate to Help > About to confirm the current installed version.
- 2. Visit the official Adobe Substance 3D Painter download page at helpx.adobe.com to obtain version 11.1.3 or later.
- 3. Download the installer for the fixed version (11.1.3 or newer).
- 4. Close any running instances of Substance 3D Painter.
- 5. Run the installer and follow the on-screen prompts to complete the update.
- 6. After installation, verify the updated version by checking Help > About to confirm version 11.1.3 or later is installed.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27217 — 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-27217 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