dbcve.org
Substance 3d StagerApplication · Adobe

CVE-2026-21342

HIGH · 7.8 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 3.1.7 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.6 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 confidence

Substance3D Stager versions 3.1.6 and earlier contain an out-of-bounds write vulnerability during file parsing that allows an attacker to execute arbitrary code in the context of the current user by tricking the victim into opening a specially crafted malicious file.

MitigationUpdate Substance3D Stager to a version newer than 3.1.6. Avoid opening untrusted or unexpected 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.7

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. Locate Adobe Substance 3D Stager installation directory
    Check common installation paths: Windows typically uses C:\Program Files\Adobe\Adobe Substance 3D Stager or %LOCALAPPDATA%\Adobe\Adobe Substance 3D Stager. On macOS check /Applications/Adobe Substance 3D Stager or ~/Applications/Adobe Substance 3D Stager.
    Affected if The application is installed on the system
  2. Identify installed version number
    Right-click the executable (e.g., Adobe Substance 3D Stager.exe on Windows or the app bundle on macOS), select Properties, then Details. Alternatively, open the application and check Help > About Adobe Substance 3D Stager.
    Affected if Unable to retrieve version information indicates potential incomplete installation or non-standard deployment
  3. Compare version to affected range
    Verify if the installed version is 3.1.6 or earlier, or if the version cannot be determined (missing). Compare the full version string (e.g., 3.1.6.0) against the fixed version 3.1.7.
    Affected if Installed version is 3.1.6 or any earlier version (e.g., 3.1.5, 3.1.0, 2.x)
  4. Confirm file parsing functionality is accessible
    Verify the application can open scene files (.sbsar, .sbs, .fbx, .obj, or other 3D file formats that Stager supports). The vulnerability triggers during parsing of these file types.
    Affected if User can import or open 3D files into the application, which enables the attack vector

The environment is affected if Adobe Substance 3D Stager version 3.1.6 or earlier is installed and users can open external files with the application.

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

Update Substance3D Stager to a version newer than 3.1.6. Avoid opening untrusted or unexpected files from untrusted sources.

Recommended fix High confidence

Substance 3D Stager 3.1.7 or later

  1. 1. Open Adobe Creative Cloud desktop application or navigate to the Substance 3D Stager download page
  2. 2. Check the current installed version of Substance 3D Stager (Help > About in the application)
  3. 3. If the version is 3.1.6 or earlier, initiate the update through Adobe Creative Cloud or download the latest version from Adobe's official website
  4. 4. Verify the update was successful by checking the version number after installation

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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