CVE-2025-54192
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.2 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive 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 · moderate confidenceAn out-of-bounds read vulnerability exists in Substance3D Painter versions 11.0.2 and earlier that allows disclosure of sensitive memory contents when a user opens a specially crafted malicious file. The vulnerability occurs during file parsing operations and does not require elevated privileges to exploit.
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.0.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.
-
Check installed Adobe Substance 3D Painter versionOpen Substance 3D Painter and navigate to Help > About to view the exact version number displayed in the dialogAffected if Version shown is 11.0.2 or any earlier version (anything below 11.0.3)
-
Verify version from system programs listWindows: Open Control Panel > Programs and Features and locate 'Substance 3D Painter' in the list. macOS: Open Applications folder, right-click the Substance 3D Painter app, select Get InfoAffected if Listed version is 11.0.2 or earlier
-
Check application file version propertyNavigate to the installation directory (typically C:\Program Files\Adobe\Adobe Substance 3D Painter\ on Windows or /Applications/Adobe Adobe Substance 3D Painter on macOS), right-click the main executable, select Properties, then view the Details tab for version infoAffected if File version property indicates 11.0.2 or prior
-
Confirm vulnerability trigger conditionRecall whether any untrusted or unexpected .ssp (Substance) files have been opened in this installation. The flaw activates during file parsing of specially crafted filesAffected if Untrusted files were opened and the version is in the affected range
User is affected if Adobe Substance 3D Painter version is 11.0.2 or earlier (below 11.0.3) and the application is used to open external 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.0.3
Update Substance3D Painter to a version newer than 11.0.2 when Adobe releases the security patch, and refrain from opening untrusted or unexpected files until the update is applied.
11.0.3
- Upgrade Adobe Substance 3D Painter to version 11.0.3 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54192 — 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-2025-54192 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