dbcve.org
Substance 3d StagerApplication · Adobe

CVE-2026-21344

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

Adobe Substance3D Stager versions 3.1.6 and earlier contain an out-of-bounds read vulnerability when parsing specially crafted files. The vulnerability allows reading past the end of an allocated memory buffer, which can be leveraged for arbitrary code execution in the context of the current user.

MitigationApply the vendor patch when available. Until then, avoid opening untrusted .sbsar or other 3D staging files from unverified 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. Verify Adobe Substance 3D Stager installation
    Open Windows Settings > Apps & features or macOS Applications folder. Search for 'Substance 3D Stager' to confirm it is installed on the system.
    Affected if The application is found installed on the system.
  2. Identify installed version
    Launch Adobe Substance 3D Stager. Navigate to Help > About (or the application menu on macOS) to display the version information. Alternatively, check the Windows Programs list or macOS Applications folder for the version number displayed alongside the application name.
    Affected if The displayed version is 3.1.6 or earlier, or any version below 3.1.7.
  3. Check for .sbsar file association
    Right-click any .sbsar file in Windows Explorer or Finder and view the 'Open with' program association. Verify if Adobe Substance 3D Stager is set as the default handler for .sbsar files.
    Affected if Adobe Substance 3D Stager is associated as the default opener for .sbsar files and the installed version is below 3.1.7.
  4. Review recent file activity
    Open Adobe Substance 3D Stager and check the recent files list (File > Recent Files). Note any .sbsar or other 3D staging files opened from untrusted or unknown sources.
    Affected if Recent .sbsar files from untrusted sources were opened and the application version is below 3.1.7.

A user is affected if Adobe Substance 3D Stager version 3.1.6 or earlier is installed, as the out-of-bounds read vulnerability can be triggered when parsing specially crafted .sbsar or 3D staging 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

Apply the vendor patch when available. Until then, avoid opening untrusted .sbsar or other 3D staging files from unverified sources.

Recommended fix High confidence

Adobe Substance 3D Stager version 3.1.7

  1. Close any running instances of Adobe Substance 3D Stager
  2. Open the Adobe Creative Cloud desktop application on your system
  3. Navigate to the 'Apps' or 'All Apps' section
  4. Locate 'Substance 3D Stager' in the application list
  5. Click the 'Update' or 'Install' button next to Substance 3D Stager to install version 3.1.7
  6. Wait for the update to complete and verify the installation finished successfully
  7. Launch Substance 3D Stager and confirm the version number displays as 3.1.7 or later

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

Fix this in Substance 3d Stager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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