dbcve.org
Substance 3d StagerApplication · Adobe

CVE-2025-61834

HIGH · 7.8 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 3.1.6 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 - Stager versions 3.1.5 and earlier are affected by a Use After Free 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 Use After Free vulnerability in Adobe Substance3D Stager versions 3.1.5 and earlier allows arbitrary code execution when a victim opens a malicious file, as the vulnerability permits memory corruption that can be leveraged for code execution in the current user's context.

MitigationUpdate Substance3D Stager to a version newer than 3.1.5 when the vendor patch is available, and exercise caution when opening files from untrusted sources.

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 StagerApplication
Affected:< 3.1.6

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 Stager is installed
    On Windows, check for the application in Add/Remove Programs or search for 'Substance 3D Stager' in the Start menu. On macOS, check /Applications folder for 'Substance 3D Stager'.
    Affected if The software is present on the system
  2. Identify the installed version number
    On Windows: Open the app, go to Help > About Substance 3D Stager, or right-click the application in Add/Remove Programs and select Properties to view the version. On macOS: Right-click the app in Applications, select Get Info, and check the Version field.
    Affected if The version shown is 3.1.5 or earlier, or the version cannot be determined (older installs may not display version in UI)
  3. Compare against the affected version range
    Check if the installed version is less than 3.1.6. The vulnerable versions are 3.1.5 and all earlier versions.
    Affected if The installed version is 3.1.5 or any version number lower than 3.1.6
  4. Determine if the application processes files from external sources
    Review whether the system user opens .staging, .sbsar, or other Substance 3D file formats, particularly from untrusted or external sources like email attachments or downloads.
    Affected if Users routinely open files in Substance3D Stager, especially from untrusted sources - this is the attack vector required for exploitation

A system is affected if Adobe Substance3D Stager version 3.1.5 or earlier is installed and users open files with the application, since the Use After Free vulnerability triggers during file processing.

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 3.1.6 or later
Fixed in 3.1.6
Interim mitigation

Update Substance3D Stager to a version newer than 3.1.5 when the vendor patch is available, and exercise caution when opening files from untrusted sources.

Recommended fix High confidence

3.1.6 or later

  1. 1. Open Adobe Substance 3D Stager and verify the current version by navigating to Help > About (or checking the application info in your system)
  2. 2. Navigate to the official Adobe support page at helpx.adobe.com to download the latest version
  3. 3. Download Substance 3D Stager version 3.1.6 or later
  4. 4. Close Adobe Substance 3D Stager if it is currently running
  5. 5. Uninstall the current version of Substance 3D Stager from your system
  6. 6. Install the newly downloaded version 3.1.6 or later
  7. 7. Restart the application and confirm the version is 3.1.6 or higher

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

Fix this in Substance 3d Stager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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