CVE-2023-26384
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 confidenceA Use After Free vulnerability in Adobe Substance 3D Stager versions 2.0.1 and earlier allows arbitrary code execution through a malicious file. The vulnerability involves memory corruption where freed memory is accessed after deallocation, potentially enabling an attacker to execute arbitrary code in the context of the current user's session.
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.
-
Check if Adobe Substance 3D Stager is installedOpen Windows Settings > Apps & Features or macOS Applications folder, look for 'Adobe Substance 3D Stager' in the installed programs listAffected if The product is listed as installed on the system
-
Determine the installed version numberRight-click the application in the apps list and select 'Modify' or 'Properties', or launch the application and go to Help > About Adobe Substance 3D Stager to view the versionAffected if A version number is displayed in the format such as 2.0.x, 1.x.x, or similar
-
Compare your version against the affected rangeCompare the displayed version to 2.0.1 - if the version is 2.0.1 or any earlier version (e.g., 2.0.0, 1.x), the installed version falls within the affected rangeAffected if The installed version is 2.0.1 or lower (for example, 2.0.0, 1.5.2, etc.)
-
Assess file handling exposureReview whether the system or users routinely open 3D scene files (.glb, .fbx, .obj, .usd, .sbsar) from external or untrusted sources, or use the application to preview files from downloads or network sharesAffected if Users open files from untrusted or unknown sources using the application
The system is affected if Adobe Substance 3D Stager version 2.0.1 or earlier is installed and users open files 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.
From vendor dataUpdate Adobe Substance 3D Stager to the latest patched version. Until then, avoid opening files from untrusted sources and consider deploying endpoint protection capable of detecting memory corruption exploits.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26384 — 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-26384 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