dbcve.org
Substance 3d StagerApplication · Adobe

CVE-2023-26383

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 Stack-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

Adobe Substance 3D Stager versions 2.0.1 and earlier contain a stack-based buffer overflow vulnerability in file parsing logic. When processing a specially crafted malicious file, the application fails to properly validate buffer boundaries, allowing an attacker to overwrite stack memory and achieve arbitrary code execution in the context of the current user.

MitigationApply the vendor patch from Adobe when available. Until then, instruct users to avoid opening untrusted .stg or other supported file formats in Adobe Substance 3D Stager, and consider deploying endpoint detection solutions to flag suspicious file operations.

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 version of Adobe Substance 3D Stager
    Open the application, then go to Help > About to display the version number. Alternatively, on Windows use PowerShell to query the registry: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Substance*Stager*'} | Select-Object DisplayName, DisplayVersion
    Affected if The displayed version is 2.0.1 or any version lower than 2.0.1
  2. Confirm application is the specific affected product
    Verify the product name in the About dialog or registry output shows 'Substance 3D Stager' (not other Substance 3D applications like Painter or Designer)
    Affected if The product is Adobe Substance 3D Stager and version is 2.0.1 or earlier
  3. Determine if the system processes untrusted .stg files
    Review recent file access logs, endpoint detection telemetry, or ask users if they commonly open files from untrusted or unknown sources in the application
    Affected if Users open .stg or supported file formats from untrusted or unknown sources in Adobe Substance 3D Stager

A system is affected if Adobe Substance 3D Stager version 2.0.1 or earlier is installed and users process untrusted files with the application.

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 the vendor patch from Adobe when available. Until then, instruct users to avoid opening untrusted .stg or other supported file formats in Adobe Substance 3D Stager, and consider deploying endpoint detection solutions to flag suspicious file operations.

Recommended fix Moderate confidence

Adobe Substance 3D Stager version higher than 2.0.1 (refer to Adobe security bulletin for exact fixed version)

  1. 1. Open a web browser and navigate to the Adobe Security Bulletin page at helpx.adobe.com/security/products/substance3d-stager.html
  2. 2. Locate the security update for CVE-2023-26383
  3. 3. Download the latest version of Adobe Substance 3D Stager recommended in the security bulletin
  4. 4. Close any running instances of Adobe Substance 3D Stager
  5. 5. Run the installer and follow the on-screen prompts to update the software
  6. 6. After installation, verify the version number matches the fixed release specified in the Adobe security bulletin
Caveat Users should review Adobe's release notes for any feature changes between versions

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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