CVE-2023-26392
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 · uneditedAdobe Substance 3D Stager version 2.0.1 (and earlier) is affected by a Use After Free 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 confidenceAdobe Substance 3D Stager versions 2.0.1 and earlier contain a Use After Free vulnerability that allows arbitrary code execution when a victim opens a malicious file. The vulnerability occurs when memory is accessed after it has been freed, potentially allowing an attacker to control execution flow.
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<= 2.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Adobe Substance 3D Stager is installedCheck for the application in the system program directory (Windows: Program Files or Program Files (x86)\Adobe\Adobe Substance 3D Stager; macOS: /Applications/Adobe Substance 3D Stager) or review installed programs via Control Panel (Windows) or Finder (macOS)Affected if The application is present on the system
-
Locate the installed executable versionRight-click the Adobe Substance 3D Stager executable (Stager.exe on Windows, Adobe Substance 3D Stager.app on macOS), select Properties, and view the Details tab for the File Version or Product VersionAffected if The executable version cannot be determined or is <= 2.0.1
-
Check version via application launchLaunch the application and navigate to Help > About Adobe Substance 3D Stager to display the exact version number shown in the About dialogAffected if The displayed version is 2.0.1 or any version lower than 2.0.1
-
Inspect registry for version on WindowsOpen Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Substance 3D Stager or HKEY_CURRENT_USER\SOFTWARE\Adobe\Adobe Substance 3D Stager to find the version valueAffected if The registry version value indicates 2.0.1 or earlier
-
Confirm vulnerability trigger conditionThe vulnerability requires a user to open a malicious file; review recent files opened by the application in the application's recent files list or system file access logsAffected if The application was used to open files from untrusted or unknown sources
The system is affected if Adobe Substance 3D Stager version 2.0.1 or earlier is installed and the application was used to open files, particularly from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Adobe Substance 3D Stager to the latest version; avoid opening files from untrusted sources.
Adobe Substance 3D Stager version 2.0.2 or later
- Visit the Adobe Security Bulletin page at helpx.adobe.com to find the specific security update for CVE-2023-26392
- Download and install the latest version of Adobe Substance 3D Stager from the official Adobe website
- Verify the installed version is greater than 2.0.1 after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26392 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-26392 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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