CVE-2025-54187
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 write vulnerability that could result in arbitrary code execution in the context of the current user. 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 confidenceSubstance3D Painter versions 11.0.2 and earlier contain an out-of-bounds write vulnerability in their file parsing logic. An attacker can craft a malicious file that, when opened by a victim, triggers the memory corruption and allows arbitrary code execution in the context of the current user.
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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 the installed version of Adobe Substance 3D PainterOpen the application and navigate to Help > About, or check the version through your system's installed programs listAffected if The version shown is 11.0.2 or earlier (any version below 11.0.3)
-
Confirm the exact version numberLocate the full version string displayed in the application's About window or installed programs detailsAffected if The version is 11.0.2, 11.0.1, 11.0.0, or any earlier version
-
Determine if the application processes files from external sourcesIdentify whether the user or other users on this system open .sbsar, .sbs, or other Substance 3D file types received from other partiesAffected if Files from untrusted or unknown sources are opened with this application
-
Assess user contextNote which user account runs Substance 3D Painter - the vulnerability executes code in the context of that current userAffected if The application runs under a privileged account (such as administrator), as the exploit would then inherit those elevated privileges
You are affected if Adobe Substance 3D Painter is installed at version 11.0.2 or earlier and the application is used to open files, particularly from untrusted sources.
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
Upgrade Substance3D Painter to a version newer than 11.0.2. Until patched, avoid opening files from untrusted sources.
11.0.3
- Open Adobe Creative Cloud desktop application
- Navigate to the "Apps" section
- Find Adobe Substance 3D Painter in the list of installed apps
- Click the "Update" button next to Substance 3D Painter
- Wait for the update to download and install
- Restart Adobe Substance 3D Painter after the update completes
- Verify the installed version is 11.0.3 by checking Help > About in the application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54187 — 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-54187 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