CVE-2025-49560
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 - Viewer versions 0.25 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 confidenceAdobe Substance3D Viewer versions 0.25 and earlier contain a heap-based buffer overflow vulnerability that can be triggered when a user opens a specially crafted malicious file, potentially allowing arbitrary code execution with the privileges of the current user.
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< 0.25.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate Adobe Substance3D Viewer installationCheck for the application in typical installation directories: Windows - C:\Program Files\Adobe\Adobe Substance 3D Viewer\ or C:\Program Files (x86)\Adobe\Adobe Substance 3D Viewer\; macOS - /Applications/Adobe Substance 3D Viewer.app. Also verify via Add/Remove Programs (Windows) or System Settings > Apps (Windows 10/11).Affected if The application is found installed on the system
-
Identify installed version numberOn Windows, right-click the executable (e.g., Adobe Substance 3D Viewer.exe) in the installation folder, select Properties, and view the File Version on the Details tab. On macOS, right-click the app bundle in Applications, select Get Info, and read the Version field under General.Affected if A version number is returned from the executable or app bundle
-
Compare version against affected rangeCompare the identified version to the affected range: versions 0.25 and earlier are vulnerable. Versions 0.25.1 and later are patched.Affected if The installed version is 0.25 or earlier (e.g., 0.25, 0.24.x, etc.)
A user is affected if Adobe Substance3D Viewer is installed and the installed version is less than 0.25.1.
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 · scoped0.25.1
Apply the vendor-supplied patch or update Substance3D Viewer to a version newer than 0.25. Users should avoid opening untrusted .3d or related files until the patch is applied.
0.25.1
- Close any running instances of Substance 3D Viewer
- Navigate to the official Adobe Substance 3D Viewer download page at helpx.adobe.com
- Download Substance 3D Viewer version 0.25.1 or later
- Run the installer and follow the prompts to install the updated version
- Launch Substance 3D Viewer and verify the version shows 0.25.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49560 — 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-49560 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