dbcve.org
Substance 3d StagerApplication · Adobe

CVE-2026-21343

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

Substance3D Stager contains an out-of-bounds read vulnerability in its file parsing logic when processing a specially crafted malicious file. The vulnerability allows reading past the end of an allocated memory structure, which can be leveraged to achieve arbitrary code execution in the context of the current user.

MitigationAvoid opening untrusted or unverified files in Substance3D Stager. Update to a patched version once released by Adobe that addresses this vulnerability.

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. Verify Adobe Substance 3D Stager is installed
    Locate the installation directory or check system inventory for Adobe Substance 3D Stager
    Affected if The software is present on the system and a vulnerable version exists
  2. Determine installed version number
    Access the application's version information through the program menu, executable properties, or system-installed programs list
    Affected if The version number is lower than 3.1.7
  3. Compare version against affected range
    Document the exact version string found and compare it to the affected range of versions below 3.1.7
    Affected if Installed version is any release prior to 3.1.7
  4. Assess file handling exposure
    Identify whether the system or user profile directories contain sample/imported 3D files that could be malicious
    Affected if Untrusted or unverified files exist in accessible locations that could be opened by the application

A user is affected if Adobe Substance 3D Stager version 3.1.7 or later is not installed, as the vulnerability exists in versions prior to 3.1.7 and triggers when processing specially crafted files.

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

Avoid opening untrusted or unverified files in Substance3D Stager. Update to a patched version once released by Adobe that addresses this vulnerability.

Recommended fix High confidence

Adobe Substance 3D Stager 3.1.7

  1. Check the current version of Adobe Substance 3D Stager by opening the application and navigating to Help > About
  2. Close any running instances of Adobe Substance 3D Stager
  3. Download Adobe Substance 3D Stager version 3.1.7 or later from the official Adobe website (helpx.adobe.com)
  4. Run the installer and follow the on-screen prompts to complete the installation
  5. Launch the application and verify the version by navigating to Help > About to confirm version 3.1.7 is installed

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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