CVE-2025-61805
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 - Stager versions 3.1.4 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code 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 confidenceOut-of-bounds read vulnerability in Substance3D Stager when parsing crafted files. The application reads past the end of an allocated memory structure during file parsing, which can be leveraged for code execution in the context of the current user. Exploitation requires user interaction (opening a malicious file).
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< 3.1.5CVSS 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 the Adobe Substance 3D Stager installationFind the application executable (Stager.exe on Windows or Adobe Substance 3D Stager.app on macOS) in the installation directory, commonly under Program Files/Adobe or /ApplicationsAffected if The application is installed on the system
-
Determine the installed version numberOpen the application, then access Help menu and select 'About Adobe Substance 3D Stager' to display the version information. Alternatively, right-click the executable, select Properties, and check the File Details or Version tabAffected if The displayed version is lower than 3.1.5 (for example, 3.1.4, 3.1.3, 3.0.x, etc.)
-
Confirm file parsing functionality is in useThe vulnerability is triggered when the application parses file formats (such as .sbsar, .sbs, or supported 3D asset files). Verify that the user has the ability to open or import files within the applicationAffected if The user can open, import, or load external files into the application (this is a default capability)
-
Check if untrusted files have been opened recentlyReview recent file open operations or check the application's recent files list to see if any files from untrusted sources were openedAffected if A crafted malicious file from an untrusted source was opened in the application
The environment is affected if Adobe Substance 3D Stager version 3.1.4 or earlier is installed and the application has been used to open files, particularly from untrusted sources, as the out-of-bounds read occurs during file parsing.
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 · scoped3.1.5
Avoid opening files from untrusted or unverified sources. Apply vendor patches when available to address the memory handling vulnerability in file parsing.
3.1.5
- Close any running instances of Substance 3D Stager
- Download the updated version of Substance 3D Stager (version 3.1.5 or later) from the official Adobe source at helpx.adobe.com
- Install or update to Substance 3D Stager version 3.1.5
- Restart the application if necessary to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.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 $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61805 — 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-61805 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