Substance 3d ViewerApplication · Adobe

CVE-2025-54244

HIGH · 7.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 0.25.2 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 - Viewer versions 0.25.1 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

A heap-based buffer overflow vulnerability in Adobe Substance3D Viewer versions 0.25.1 and earlier allows arbitrary code execution through a maliciously crafted 3D file opened by the victim. The vulnerability exists in the file parsing/processing component and can be triggered upon file load.

MitigationUpgrade Substance3D Viewer to a version newer than 0.25.1 when a patch is available. Until then, avoid opening untrusted 3D model files in the application.

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 ViewerApplication
Affected:< 0.25.2

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. Verify Adobe Substance3D Viewer installation
    Check for the application in typical installation directories (Windows: C:\Program Files\Adobe\Adobe Substance 3D Viewer, macOS: /Applications/Adobe Substance 3D Viewer) or look for the executable named 'Adobe Substance 3D Viewer.exe' or similar using file system search
    Affected if The application is found installed on the system
  2. Determine installed version number
    Right-click the executable or application icon, select Properties, and check the Version tab. Alternatively, locate the application in Add/Remove Programs (Windows) or Applications folder (macOS) to view the installed version
    Affected if The installed version is 0.25.1 or any version earlier than 0.25.2
  3. Confirm file parsing component is active
    The vulnerability is in the file parsing/processing component that handles 3D model files. Check if the application has been used to open or preview 3D files recently by reviewing recent files or application logs if available
    Affected if The application has been used to open 3D files and the vulnerable version (below 0.25.2) is installed
  4. Assess exposure to untrusted 3D files
    Review the source of 3D files opened with the application. Determine if files from untrusted or unknown sources (downloads, email attachments, external drives) have been opened in the vulnerable version
    Affected if The vulnerable version (below 0.25.2) is installed AND the application has processed 3D files from untrusted or unknown sources

A user is affected if Adobe Substance3D Viewer version 0.25.1 or earlier is installed AND the file parsing component has been used to open 3D files, particularly 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 0.25.2 or later
Fixed in 0.25.2
Interim mitigation

Upgrade Substance3D Viewer to a version newer than 0.25.1 when a patch is available. Until then, avoid opening untrusted 3D model files in the application.

Recommended fix High confidence

0.25.2

  1. Upgrade Substance 3D Viewer to version 0.25.2 or later

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

Fix this in Substance 3d Viewer Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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