CVE-2026-21365
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 an out-of-bounds read vulnerability that could lead to memory exposure. An attacker could leverage this vulnerability to access sensitive information stored in memory. 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 confidenceAdobe Substance3D Painter versions 11.1.2 and earlier contain an out-of-bounds read vulnerability during file parsing. When a victim opens a specially crafted malicious file, the application reads memory beyond allocated buffer boundaries, potentially exposing sensitive data from the process memory space.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Verify Adobe Substance 3D Painter installationOn Windows, check Program Files/Adobe or the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Adobe Substance 3D Painter'. On macOS, check /Applications for Adobe Substance 3D Painter.appAffected if The application is installed on the system
-
Determine installed version numberLaunch the application and navigate to Help > About Adobe Substance 3D Painter, or on Windows check the version in Add/Remove Programs. On macOS, right-click the app > Get Info to see the version.Affected if A version number is displayed in the About dialog or app info
-
Compare version to affected rangeCompare your installed version against the affected range: versions 11.1.2 and earlier are vulnerable. Version 11.1.3 or later contains the fix.Affected if The installed version is 11.1.2 or earlier, or any version below 11.1.3
-
Assess file handling exposureDetermine if the system user profile has permission to open or import files within Substance 3D Painter, as the vulnerability triggers during file parsing operations.Affected if Users can open or import files in the application, which is the normal and intended use of the software
The system is affected if Adobe Substance 3D Painter version 11.1.2 or earlier is installed and users can open or import files, as the vulnerability is triggered during normal file parsing operations.
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
Restrict file handling permissions and educate users to avoid opening files from untrusted sources. Monitor for vendor patches and apply updates promptly once available.
Substance 3D Painter 11.1.3
- 1. Back up any custom assets, brushes, or projects from your current Substance 3D Painter installation
- 2. Uninstall the current version of Substance 3D Painter (versions 11.1.2 and earlier)
- 3. Navigate to the official Adobe website and download Substance 3D Painter version 11.1.3 or later from helpx.adobe.com
- 4. Install the downloaded version of Substance 3D Painter
- 5. Verify the installed version by checking Help > About in the application menu to confirm version 11.1.3 or higher is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21365 — 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-21365 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