Substance 3d StagerApplication · Adobe

CVE-2026-21287

HIGH · 7.8 CVSS v3.1 Published 2026-01-13
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. The vulnerability exploits memory that has been deallocated but is still being accessed, potentially enabling an attacker to execute arbitrary code with the privileges of the current user.

MitigationUpdate Substance3D Stager to a patched version once released by Adobe. Avoid opening untrusted or unsolicited files, and implement application allowlisting to reduce the attack surface.

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. Identify if Adobe Substance3D Stager is installed
    Check for the application in the system program files directory (typically C:\Program Files\Adobe\Adobe Substance 3D Stager) or look for the application entry in Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
    Affected if The application is present on the system
  2. Determine the installed version number
    Open the application and navigate to Help > About Adobe Substance3D Stager, or check the version in the application executable properties (right-click the .exe file and view Details), or query the Windows Registry for the version string
    Affected if The displayed version is 3.1.5 or any version number lower than 3.1.6
  3. Verify the file open functionality is accessible
    Confirm the application can normally open and load 3D scene files (this is the attack vector for the vulnerability)
    Affected if The application is installed and functional, allowing users to open files - which is the normal behavior that triggers the vulnerability

A user is affected if Adobe Substance3D Stager version 3.1.5 or earlier is installed and the application can open files, since the Use After Free vulnerability triggers when opening a malicious file.

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 patched version once released by Adobe. Avoid opening untrusted or unsolicited files, and implement application allowlisting to reduce the attack surface.

Recommended fix High confidence

Substance 3D Stager 3.1.6

  1. Navigate to the Adobe Creative Cloud desktop application or the Substance 3D Stager application
  2. Check for available updates or navigate to the application's help menu
  3. Select 'Check for Updates' or navigate to Adobe's official download page for Substance 3D Stager
  4. Download and install Substance 3D Stager version 3.1.6 or later
  5. Restart the application after installation to ensure the update is fully applied

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21287 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