CVE-2023-26403
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 an out-of-bounds read 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 · high confidenceAdobe Substance 3D Stager version 2.0.1 and earlier contains an out-of-bounds read vulnerability that allows a maliciously crafted file to read memory outside allocated bounds when opened by a victim. This can expose sensitive memory contents and potentially facilitate bypass of ASLR and other memory protection mitigations.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Adobe Substance 3D Stager is installedCheck for the application in the system: On Windows, look in Program Files or Program Files (x86) for 'Adobe Substance 3D Stager' folder, or check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry containing 'Substance 3D Stager'. On macOS, check /Applications for Adobe Substance 3D Stager.app.Affected if The application is present on the system.
-
Determine the installed version numberAccess the application's version information: On Windows, right-click the executable or check the registry uninstall entry for the DisplayVersion value. On macOS, right-click Adobe Substance 3D Stager.app, select Get Info, and read the Version field.Affected if Unable to determine version, but the application is installed.
-
Compare installed version to affected rangeCompare the obtained version number to the affected versions. Affected versions are 2.0.1 and earlier. If your version is 2.0.1 or any earlier version (such as 2.0.0, 1.x.x), you are within the affected range.Affected if Installed version is 2.0.1 or earlier.
-
Confirm vulnerability trigger conditionThe vulnerability is triggered when a victim opens a maliciously crafted file. Review recent files opened in Adobe Substance 3D Stager, particularly from untrusted or unknown sources.Affected if Any file was opened in the application, regardless of source, while running an affected version.
A user is affected if Adobe Substance 3D Stager version 2.0.1 or earlier is installed and was used to open files.
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 a version newer than 2.0.1 when a patch is available. Additionally, exercise caution when opening files from untrusted sources, as exploitation requires user interaction.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26403 — 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-26403 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