dbcve.org
Substance 3d StagerApplication · Adobe

CVE-2025-61833

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 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 confidence

Substance3D Stager versions 3.1.5 and earlier contain an out-of-bounds read vulnerability when parsing specially crafted files. The vulnerability occurs due to insufficient bounds checking during file parsing, allowing reading past the end of allocated memory structures. An attacker can exploit this by convincing a user to open a malicious file, potentially achieving code execution in the context of the current user.

MitigationUsers should avoid opening files from untrusted sources. Organizations should update Substance3D Stager to a version newer than 3.1.5 once a patched release is available from Adobe.

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. Check if Adobe Substance 3D Stager is installed
    On Windows, check for the installation directory at C:\Program Files\Adobe\Adobe Substance 3D Stager or C:\Program Files (x86)\Adobe\Adobe Substance 3D Stager. On macOS, check /Applications/Adobe Substance 3D Stager.app. Alternatively, search for the executable named 'Adobe Substance 3D Stager.exe' (Windows) or the application bundle (macOS).
    Affected if The application directory or executable is found on the system.
  2. Determine the installed version number
    On Windows, right-click the executable or launcher file, select Properties, and look at the Version tab. On macOS, right-click the application in Finder, select Get Info, and check the version field. You can also look for a version file in the application installation folder.
    Affected if The version cannot be determined or the application is not found.
  3. Compare installed version against affected range
    If the version is found, compare it to 3.1.6. Versions 3.1.5 and earlier (including all 3.1.x versions below 3.1.6, 3.0.x, 2.x, and 1.x) are within the affected range.
    Affected if The installed version is 3.1.5 or any version lower than 3.1.6.

A user is affected if Adobe Substance 3D Stager is installed and the running version is 3.1.5 or earlier (any version below 3.1.6).

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

Users should avoid opening files from untrusted sources. Organizations should update Substance3D Stager to a version newer than 3.1.5 once a patched release is available from Adobe.

Recommended fix High confidence

Adobe Substance 3D Stager version 3.1.6

  1. Check current Adobe Substance 3D Stager version by opening the application and navigating to Help > About, or checking in the Creative Cloud desktop app
  2. Open Adobe Creative Cloud desktop application and navigate to the Apps section
  3. Find Adobe Substance 3D Stager in the installed apps list
  4. Click Update or Install to get the latest version (3.1.6 or later)
  5. Alternatively, download the update directly from helpx.adobe.com by searching for Substance 3D Stager updates
  6. Launch the updated application and verify 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
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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