Substance 3d ModelerApplication · Adobe

CVE-2025-27173

HIGH · 7.8 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to after 1.15.0 or later.
See remediation →
81/100
Remediation priority · High
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 - Modeler versions 1.15.0 and earlier are affected by a Heap-based Buffer Overflow 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 confidence

Substance3D Modeler versions 1.15.0 and earlier contain a heap-based buffer overflow vulnerability in their file parsing logic. An attacker can craft a malicious file that, when opened by a victim, triggers the overflow and allows arbitrary code execution in the context of the current user.

MitigationUpdate Substance3D Modeler to a version newer than 1.15.0. Until updated, avoid opening files from untrusted sources.

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 ModelerApplication
Affected:<= 1.15.0

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

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

  1. Check if Adobe Substance 3D Modeler is installed
    On Windows, check Program Files and Program Files (x86) for the Substance 3D Modeler folder, or use Add/Remove Programs. On macOS, check /Applications for Substance 3D Modeler.app.
    Affected if The software is present on the system
  2. Determine the installed version of Substance 3D Modeler
    On Windows, right-click the executable or launcher, select Properties, and check the Version or Details tab for the product version. On macOS, right-click the app, select Get Info, and check the Version field.
    Affected if The version cannot be determined or the software is installed without version info
  3. Compare your installed version to the affected range
    Review the version number found in the previous step against the affected range: any version 1.15.0 or earlier is vulnerable.
    Affected if The installed version is 1.15.0 or any earlier version number (for example, 1.14.0, 1.10.0, 1.0.0)
  4. Identify the file parsing component
    The vulnerability exists in the file parsing logic that handles model files opened within Substance 3D Modeler. No additional configuration check is needed; the vulnerability is present in the core application.
    Affected if Substance 3D Modeler version 1.15.0 or earlier is running

If Adobe Substance 3D Modeler version 1.15.0 or earlier is installed, the environment is affected by this CVE.

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 a release after 1.15.0
Interim mitigation

Update Substance3D Modeler to a version newer than 1.15.0. Until updated, avoid opening files from untrusted sources.

Recommended fix Moderate confidence

Substance 3D Modeler 1.16.0 or later

  1. Navigate to the Adobe Substance 3D Modeler download page or open the Adobe Creative Cloud desktop application
  2. Check for and install any available updates for Substance 3D Modeler
  3. Verify the installed version by going to Help > About in the application menu
  4. Confirm the version number is 1.16.0 or later to ensure the security patch is applied

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

Fix this in Substance 3d Modeler Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27173 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