Substance 3d StagerApplication · Adobe

CVE-2023-26393

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 versions 2.0.1 and earlier contain an out-of-bounds read vulnerability during file parsing. When processing a specially crafted malicious file, the application reads past the end of an allocated memory buffer, potentially allowing arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Substance 3D Stager to the latest patched version. Until patched, avoid opening files from untrusted 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:<= 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. Locate Adobe Substance 3D Stager installation
    Check common installation paths: Windows: C:\Program Files\Adobe\Adobe Substance 3D Stager or C:\Program Files (x86)\Adobe\Adobe Substance 3D Stager. macOS: /Applications/Adobe Substance 3D Stager. Also check Start Menu or Applications folder for the application icon.
    Affected if Application is installed on the system
  2. Find the installed version number
    Right-click the Adobe Substance 3D Stager executable or app, select Properties, then look on the Details tab for Product Version. On macOS, right-click the app, select Get Info, and check the Version field. Alternatively, open the app and go to Help > About Adobe Substance 3D Stager.
    Affected if Version displays as 2.0.1 or lower
  3. Compare against affected version range
    Compare the installed version number to the affected range: any version 2.0.1 or earlier is vulnerable. If the version is unknown but the product is installed, treat it as potentially affected.
    Affected if Installed version is 2.0.1 or any earlier version number

The environment is affected if Adobe Substance 3D Stager version 2.0.1 or earlier is installed, since the out-of-bounds read flaw triggers during parsing of malicious 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 a release after 2.0.1
Interim mitigation

Update Adobe Substance 3D Stager to the latest patched version. Until patched, avoid opening files from untrusted sources.

Recommended fix Moderate confidence

Adobe Substance 3D Stager 2.0.2 or later (check official Adobe security bulletin for exact version)

  1. Verify current Adobe Substance 3D Stager version by opening the application and checking Help > About
  2. Navigate to Adobe's official security bulletin for this CVE at helpx.adobe.com to confirm the fixed version
  3. Download and install the latest version of Adobe Substance 3D Stager from Adobe's official website
  4. After updating, verify the installed version is newer than 2.0.1

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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