dbcve.org
Substance 3d PainterApplication · Adobe

CVE-2025-54193

MEDIUM · 5.5 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 11.0.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.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 confidence

An out-of-bounds read vulnerability exists in Substance3D Painter's file parsing logic. When processing a maliciously crafted file, the application reads memory beyond allocated buffer boundaries, potentially exposing sensitive data from the process memory space.

MitigationUsers should avoid opening files from untrusted or unknown sources. Update to a patched version of Substance3D Painter once Adobe releases a security update addressing this vulnerability.

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.0.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
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 checks

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

  1. Confirm Adobe Substance 3D Painter is installed
    Check for the application in typical installation locations: Windows: C:\Program Files\Adobe\Adobe Substance 3D Painter or C:\Program Files (x86)\Adobe\Adobe Substance 3D Painter; macOS: /Applications/Adobe Substance 3D Painter. On Linux, check common paths like /opt/Adobe/Adobe Substance 3D Painter or ~/.local/share/applications/
    Affected if The application is present on the system
  2. Identify the installed version number
    On Windows: Right-click the application executable in Program Files, select Properties, and view the Details tab for the File Version. Alternatively, open the application and go to Help > About Adobe Substance 3D Painter to view the version displayed in the UI
    Affected if Unable to determine version, or version displays as any build prior to 11.0.3
  3. Compare version against affected range
    Parse the version number identified in the previous step. Versions are typically formatted as major.minor.build (for example, 11.0.0, 10.5.2, etc.). Compare numerically: any version where the major version is less than 11, OR major version equals 11 with minor version less than 0, OR major=11 and minor=0 with build less than 3, is within the affected range
    Affected if Installed version is below 11.0.3 (such as 11.0.2, 11.0.1, 11.0.0, 10.x, 9.x, or any earlier version)
  4. Verify file parsing functionality is in use
    The vulnerability is triggered when processing maliciously crafted files. Check recent usage: look for .sbsar, .sbs, .spp, or other Substance file types that have been opened in the application. On Windows, review recent documents or application log files if available
    Affected if The application has been used to open files from untrusted or unknown sources, as this is the attack vector for triggering the out-of-bounds read

A user is affected if Adobe Substance 3D Painter version 11.0.3 or higher is not installed, and the application has been used to open files from untrusted sources.

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.0.3 or later
Fixed in 11.0.3
Interim mitigation

Users should avoid opening files from untrusted or unknown sources. Update to a patched version of Substance3D Painter once Adobe releases a security update addressing this vulnerability.

Recommended fix High confidence

Adobe Substance 3D Painter version 11.0.3

  1. 1. Close Adobe Substance 3D Painter if it is currently running
  2. 2. Navigate to the Adobe Creative Cloud desktop application or visit helpx.adobe.com
  3. 3. Locate Adobe Substance 3D Painter in your installed applications
  4. 4. Check for available updates or navigate to the product download page
  5. 5. Download and install version 11.0.3 or later
  6. 6. Verify the installation by opening Substance 3D Painter and checking the version number in the application menu (Help > About)

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

Fix this in Substance 3d Painter Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Check whether your project pulls in CVE-2025-54193 — 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-2025-54193 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