dbcve.org
Substance 3d ViewerApplication · Adobe

CVE-2025-54274

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to after 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.2 and earlier are affected by a Stack-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 · moderate confidence

Substance3D Viewer versions 0.25.2 and earlier contain a stack-based buffer overflow vulnerability that can be triggered when processing a specially crafted malicious file. Successful exploitation allows arbitrary code execution within the context of the user who opened the malicious file.

MitigationUpdate Substance3D Viewer to a version newer than 0.25.2 when a patch is released by Adobe, and exercise caution by not opening files from untrusted sources until the update is applied.

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 if Adobe Substance3D Viewer is installed
    On Windows, open Programs and Features or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName' in PowerShell to list installed programs. Look for 'Adobe Substance 3D Viewer' in the results.
    Affected if The application appears in the installed programs list.
  2. Locate the Substance3D Viewer executable
    Check common installation paths: C:\Program Files\Adobe\Adobe Substance 3D Viewer\ or C:\Program Files (x86)\Adobe\Adobe Substance 3D Viewer\. The executable is typically named 'Adobe Substance 3D Viewer.exe'.
    Affected if The executable exists at one of these locations.
  3. Determine the installed version
    Right-click the executable, select Properties, then go to the Details tab to view the File Version. Alternatively, run '(Get-Item "C:\Program Files\Adobe\Adobe Substance 3D Viewer\Adobe Substance 3D Viewer.exe").VersionInfo.FileVersion' in PowerShell.
    Affected if A version number is displayed in the file properties.
  4. Compare against affected version range
    Compare the displayed version to the affected range: any version <= 0.25.2 is vulnerable. Note that version 0.25.2 itself is also affected.
    Affected if The installed version is 0.25.2 or any earlier version (e.g., 0.25.1, 0.25.0, 0.24.x).

You are affected if Adobe Substance3D Viewer is installed and the version is 0.25.2 or earlier.

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 0.25.2
Interim mitigation

Update Substance3D Viewer to a version newer than 0.25.2 when a patch is released by Adobe, and exercise caution by not opening files from untrusted sources until the update is applied.

Recommended fix Moderate confidence

Latest available version of Substance 3D Viewer (newer than 0.25.2)

  1. 1. Open Adobe Substance 3D Viewer on your system
  2. 2. Navigate to the application's help or about section
  3. 3. Check the current version number to confirm it is 0.25.2 or earlier
  4. 4. Visit the official Adobe download center or Substance 3D Viewer product page at adobe.com
  5. 5. Download and install the latest available version of Substance 3D Viewer
  6. 6. Verify the installed version is newer than 0.25.2
  7. 7. Delete or safely handle any untrusted 3D files that may have been received from untrusted sources

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

Fix this in Substance 3d Viewer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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