dbcve.org
Substance 3d StagerApplication · Adobe

CVE-2023-26389

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 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 Substance 3D Stager version 2.0.1 and earlier contains an out-of-bounds read vulnerability when parsing specially crafted files. The vulnerability allows reading past the end of allocated memory structures, which an attacker could potentially leverage to achieve arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Substance 3D Stager to the latest patched version. Avoid opening files from untrusted or unknown sources, as exploitation requires user interaction (opening a malicious file).

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. Check if Adobe Substance 3D Stager is installed
    Open Windows Settings > Apps > Installed Apps (or Control Panel > Programs and Features) and search for 'Adobe Substance 3D Stager'. Alternatively, check the default installation path C:\Program Files\Adobe\Adobe Substance 3D Stager for the application executable.
    Affected if The application is found installed on the system
  2. Determine the installed version number
    Launch Adobe Substance 3D Stager, then go to Help > About Adobe Substance 3D Stager to display the version. Alternatively, in Windows, right-click the application in Programs and Features, select Properties, and check the Details tab for the Version field.
    Affected if A version number is displayed (any version indicates the software is present)
  3. Compare the installed version to the affected range
    Review the version found in the previous step. The affected versions are any release at or below 2.0.1. Compare your displayed version number (for example, 2.0.1, 2.0.0, 1.x.x) against this threshold.
    Affected if The installed version is 2.0.1 or any earlier version (for example, 2.0.0, 1.5.0, etc.)
  4. Assess user interaction risk (exploitation context)
    Consider whether the user routinely opens 3D scene files (.glb, .fbx, .obj, .stl, or Substance 3D's native formats) from external or untrusted sources. The vulnerability is triggered when parsing specially crafted files.
    Affected if Users open files from untrusted or unknown sources using the affected software version

The user is affected if Adobe Substance 3D Stager is installed with any version at or below 2.0.1 AND the software is used to open files from potentially 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

Update Adobe Substance 3D Stager to the latest patched version. Avoid opening files from untrusted or unknown sources, as exploitation requires user interaction (opening a malicious file).

Recommended fix Moderate confidence

Adobe Substance 3D Stager 2.1.0 or later (latest stable release)

  1. 1. Close Adobe Substance 3D Stager if it is currently running
  2. 2. Back up any existing projects and custom assets as a precaution
  3. 3. Open Adobe Creative Cloud desktop application or navigate to https://creativecloud.adobe.com
  4. 4. Locate Adobe Substance 3D Stager in the applications list
  5. 5. Click the 'Update' button next to Substance 3D Stager to install the latest version
  6. 6. Wait for the download and installation to complete
  7. 7. Launch the newly updated version of Substance 3D Stager
  8. 8. Verify the installed version by checking Help > About (or the application info panel)
Caveat Minimal risk - Adobe minor version updates typically include bug fixes and security patches without breaking existing project compatibility

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
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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