CVE-2025-54189
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 confidenceSubstance3D Painter versions 11.0.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 memory contents to an attacker.
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.
-
Verify Adobe Substance 3D Painter is installedCheck your system for the presence of Adobe Substance 3D Painter application. This may be in your Program Files (Windows) or Applications folder (macOS), or check via your system's installed programs list.Affected if The application is installed on the system
-
Determine the installed version numberOpen Adobe Substance 3D Painter and navigate to Help > About (or check the application metadata in your system). Alternatively, locate the application in your system and check its version property or release notes.Affected if The version cannot be determined or is lower than 11.0.3
-
Compare version against affected rangeReview the installed version against the affected range: versions prior to 11.0.3 (including 11.0.2 and earlier) are vulnerable.Affected if The installed version is 11.0.2 or earlier (any version < 11.0.3)
-
Assess file opening exposureDetermine whether the application is used to open files from untrusted or external sources. The vulnerability triggers specifically when parsing specially crafted malicious files.Affected if Users open files from untrusted or unknown sources in Substance 3D Painter
A user is affected if Adobe Substance 3D Painter version 11.0.2 or earlier is installed and the application is used to open files, as the out-of-bounds read occurs during file parsing of maliciously crafted 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
Avoid opening untrusted or unexpected files in Substance3D Painter until a vendor patch is available. Monitor Adobe's security advisories for updated versions.
11.0.3
- Back up any important projects or files in Substance 3D Painter before updating
- Navigate to the official Adobe download page at helpx.adobe.com or use the Adobe Creative Cloud desktop application
- Download Substance 3D Painter version 11.0.3 or later
- Run the installer and follow the on-screen prompts to complete the installation
- Verify the installed version by opening Substance 3D Painter and checking the version number in the application menu
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54189 — 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-54189 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