Substance 3d StagerApplication · Adobe

CVE-2023-26386

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-12
Fix available
A fix is available. Upgrade to after 2.0.1 or later.
See remediation →
58/100
Remediation priority · Elevated
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 Access of Uninitialized Pointer vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 · moderate confidence

Adobe Substance 3D Stager versions 2.0.1 and earlier contain an access of uninitialized pointer vulnerability that can lead to disclosure of sensitive memory contents. Successful exploitation requires a victim to open a malicious file, and the vulnerability can potentially be leveraged to bypass ASLR mitigations by leaking memory addresses.

MitigationUsers should avoid opening untrusted or unsolicited files in Adobe Substance 3D Stager until a vendor patch is available. Organizations should monitor Adobe security advisories for the patched version and prioritize updating affected systems.

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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
    On Windows, open Control Panel > Programs and Features, or right-click the application executable in the installation folder and select Properties > Details to view the File Version. On macOS, right-click the application in /Applications, select Get Info, or run: mdls -name kMDItemVersion "/Applications/Adobe Substance 3D Stager.app"
    Affected if The displayed version is 2.0.1 or any earlier version (e.g., 2.0.0, 1.x.x)
  2. Confirm application installation path
    Locate the Adobe Substance 3D Stager executable. Common paths: Windows: C:\Program Files\Adobe\Adobe Substance 3D Stager\Adobe Substance 3D Stager.exe ; macOS: /Applications/Adobe Substance 3D Stager.app
    Affected if The application is installed on the system at any version
  3. Check for recent security updates from Adobe
    Open Adobe Substance 3D Stager, go to Help > Check for Updates, or visit the Adobe security advisories page to verify if a newer version beyond 2.0.1 has been released
    Affected if No newer version is available or the installed version remains at 2.0.1 or below

You are affected if Adobe Substance 3D Stager version 2.0.1 or earlier is installed, and the vulnerability can be triggered when opening a specially crafted 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 a release after 2.0.1
Interim mitigation

Users should avoid opening untrusted or unsolicited files in Adobe Substance 3D Stager until a vendor patch is available. Organizations should monitor Adobe security advisories for the patched version and prioritize updating affected systems.

Recommended fix Moderate confidence

Substance 3D Stager 2.0.2 or later

  1. 1. Open Adobe Substance 3D Stager application
  2. 2. Navigate to the Help menu or check for updates within the application
  3. 3. If an update is available, download and install the latest version
  4. 4. Alternatively, download the latest version from the official Adobe website at adobe.com

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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