CVE-2026-27218
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 services. 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 confidenceA NULL Pointer Dereference vulnerability in Adobe Substance3D Painter versions 11.1.2 and earlier allows attackers to crash the application by providing a specially crafted malicious file. The vulnerability occurs during file parsing operations where the application attempts to dereference a NULL pointer, causing an access violation and application crash.
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.
-
Identify the installed Adobe Substance3D Painter versionOpen the application and navigate to Help > About Adobe Substance3D Painter, or check the version in the software installer or installed programs list on the systemAffected if The displayed version is 11.1.2 or earlier (any version below 11.1.3)
-
Confirm version number formatVerify the exact version number displayed (e.g., 11.1.0, 11.1.1, 11.1.2) - note that version 11.1.3 is the first patched releaseAffected if The version shows 11.1.2, 11.1.1, 11.1.0, or any earlier 11.x version
-
Understand the attack vectorThis vulnerability is triggered when the application parses a specially crafted malicious file - there is no specific configuration or feature toggle to checkAffected if The application can open external files and the installed version is vulnerable (11.1.2 or earlier)
If Adobe Substance3D Painter is installed at version 11.1.2 or any earlier version (any 11.x version below 11.1.3), the environment is affected by this vulnerability when parsing untrusted files.
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
Apply the vendor patch/upgrade to a version later than 11.1.2 when released. Until then, avoid opening files from untrusted sources and consider implementing application sandboxing or file scanning as a defensive measure.
Substance 3D Painter 11.1.3 or later
- Verify current version of Substance 3D Painter by opening the application and checking Help > About
- Close any open instances of Substance 3D Painter
- Launch Adobe Creative Cloud desktop application and navigate to the Apps tab
- Find Substance 3D Painter in the installed apps list and click Update if available, or install the application fresh if not already installed
- Alternatively, open Substance 3D Painter and go to Help > Check for Updates to trigger the update process
- Restart the application after the update completes
- Verify the updated version is 11.1.3 or later by checking Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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 $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27218 — 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-27218 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