CVE-2025-54280
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.2 and earlier are affected by an out-of-bounds write 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 confidenceSubstance3D Viewer versions 0.25.2 and earlier contain an out-of-bounds write vulnerability that allows arbitrary code execution in the current user's context. Exploitation requires the victim to open a malicious file, making this a file-based attack vector.
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.2CVSS 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 Substance 3D Viewer installationCheck common installation paths: 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 check Start Menu or Applications folder for the application icon.Affected if The application is found installed on the system.
-
Determine installed versionOn Windows: Right-click the application executable, select Properties, then look at the Details tab for File Version or Product Version. On macOS: Right-click the app, select Get Info, and check the Version field. Alternatively, check the uninstall registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Adobe Substance 3D Viewer entry.Affected if A version number of 0.25.2 or lower is reported.
-
Compare version to affected rangeIf version is obtained, compare the three-part version number (0.x.x) against the affected range: any version 0.25.2 or earlier. Version 0.25.2 and all prior 0.x.y versions are vulnerable.Affected if The installed version is 0.25.2 or any earlier version (e.g., 0.25.1, 0.25.0, 0.24.x, etc.).
-
Verify file association or recent file opening activityCheck if the application is configured to open .sbsar, .sbs, or common 3D asset file types. On Windows, check HKEY_CLASSES_ROOT for file extensions associated with the viewer. Review recent documents or temp folders for files opened by Substance3D Viewer.Affected if The application handles user-supplied 3D files and the user opens untrusted files, which is the exploitation prerequisite.
A user is affected if Adobe Substance 3D Viewer version 0.25.2 or earlier is installed and the user opens or is likely to open untrusted 3D content files.
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.
From vendor dataUpdate Substance3D Viewer to a version newer than 0.25.2. Additionally, educate users to avoid opening untrusted files and consider implementing application whitelisting or restrictions on file types the viewer can open.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54280 — 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-54280 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