Substance 3d StagerApplication · Adobe

CVE-2023-26394

HIGH · 7.8 CVSS v3.1 Published 2023-04-12
Fix available
A fix is available. Upgrade to after 2.0.1 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
Adobe Substance 3D Stager version 2.0.1 (and earlier) is affected by a Heap-based Buffer Overflow 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

Heap-based buffer overflow vulnerability in Adobe Substance 3D Stager versions 2.0.1 and earlier allows arbitrary code execution through a maliciously crafted file opened by the victim.

MitigationApply vendor patch from Adobe (version newer than 2.0.1) and instruct users to avoid opening untrusted .stager or related files.

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:<= 2.0.1

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 installed Adobe Substance 3D Stager version
    Windows: Open Programs and Features or check registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for Adobe Substance 3D Stager. MacOS: Right-click Adobe Substance 3D Stager.app > Get Info or run: defaults read /Applications/Adobe\ Substance\ 3D\ Stager.app/Contents/Info CFBundleShortVersionString
    Affected if Installed version is 2.0.1 or earlier (any version <= 2.0.1)
  2. Locate the application executable
    Windows: Typically at C:\Program Files\Adobe\Adobe Substance 3D Stager\Adobe Substance 3D Stager.exe. MacOS: /Applications/Adobe Substance 3D Stager.app/Contents/MacOS/Adobe Substance 3D Stager
    Affected if Application exists on the system regardless of version
  3. Verify application binary version
    Right-click the executable file > Properties > Details tab to view File Version and Product Version
    Affected if Product Version shows 2.0.1 or earlier
  4. Check for recent file open activity
    Review recent .stager files opened by the user. On Windows: Check recent documents or TEMP folder for .stager files. On MacOS: Check ~/Documents or recent files accessed by the application
    Affected if User has opened .stager files from untrusted sources since vulnerability is triggered by parsing malicious files

A system is affected if Adobe Substance 3D Stager version 2.0.1 or earlier is installed, and especially if users open .stager files from untrusted sources.

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 a release after 2.0.1
Interim mitigation

Apply vendor patch from Adobe (version newer than 2.0.1) and instruct users to avoid opening untrusted .stager or related files.

Recommended fix High confidence

Adobe Substance 3D Stager 2.0.2 or later

  1. Navigate to the Adobe Substance 3D Stager download page or open Adobe Creative Cloud desktop application
  2. Locate Adobe Substance 3D Stager in your installed applications
  3. Update to version 2.0.2 or later which contains the security fix
  4. Alternatively, download the updated version directly from Adobe's official website
  5. Verify the installation by checking the application version in Help > About

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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