dbcve.org
Substance 3d PainterApplication · Adobe

CVE-2026-27214

MEDIUM · 5.5 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 11.1.3 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
Substance3D - 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 confidence

A NULL Pointer Dereference vulnerability in Adobe Substance3D Painter versions 11.1.2 and earlier allows remote attackers to crash the application by tricking users into opening a specially crafted malicious file, resulting in denial of service.

MitigationUsers should avoid opening untrusted or unexpected files in Substance3D Painter until a security update is released. Organizations should consider restricting file handling capabilities and monitoring for suspicious file types.

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
Substance 3d PainterApplication
Affected:< 11.1.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Adobe Substance 3D Painter is installed
    Check the system's application list or program files for Adobe Substance 3D Painter. On Windows, look in Program Files or the Windows Registry under HKLM\SOFTWARE\Adobe. On macOS, check /Applications for Substance 3D Painter.app.
    Affected if The application is not found on the system, then this CVE does not apply.
  2. Determine the installed version number
    Open Adobe Substance 3D Painter and navigate to Help > About, or check the application information in the Windows Registry or macOS Application folder. The version is typically displayed as a three-part number like 11.1.x.
    Affected if Unable to determine the version, treat as potentially affected.
  3. Compare version against the affected range
    Check if the installed version is 11.1.2 or earlier. The affected range per the CVE is any version prior to 11.1.3.
    Affected if Installed version is 11.1.2 or lower (less than 11.1.3), indicating the application is vulnerable.
  4. Assess file opening risk
    This vulnerability requires a user to open a specially crafted malicious file. Evaluate whether users in the environment routinely open files from untrusted or external sources in Substance 3D Painter.
    Affected if Users routinely open untrusted or unexpected .sbsar or other Substance files, increasing exposure to the exploit.

The environment is affected if Adobe Substance 3D Painter version 11.1.2 or earlier is installed AND users could be tricked into opening a maliciously crafted file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.1.3 or later
Fixed in 11.1.3
Interim mitigation

Users should avoid opening untrusted or unexpected files in Substance3D Painter until a security update is released. Organizations should consider restricting file handling capabilities and monitoring for suspicious file types.

Recommended fix High confidence

Substance 3D Painter 11.1.3

  1. 1. Check the current version of Adobe Substance 3D Painter by opening the application and navigating to Help > About, or checking in the Creative Cloud desktop app
  2. 2. Download Adobe Substance 3D Painter version 11.1.3 or later from the official Adobe website at helpx.adobe.com
  3. 3. Install the updated version using the Adobe Creative Cloud desktop application or the standalone installer
  4. 4. Verify the installation was successful by confirming the version number displays 11.1.3 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Substance 3d Painter Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27214 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27214 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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