CVE-2026-27309
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 · uneditedSubstance3D - Stager versions 3.1.7 and earlier are 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 confidenceSubstance3D Stager versions 3.1.7 and earlier contain a Use After Free vulnerability that can be triggered when a user opens a malicious file. The vulnerability allows arbitrary code execution within the context of the current user session due to improper memory management.
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< 3.1.8CVSS 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 installed version on WindowsOpen Control Panel > Programs and Features, locate 'Adobe Substance 3D Stager' in the list, and note the version columnAffected if The version listed is lower than 3.1.8 or shows 3.1.7 or earlier
-
Check version on macOSOpen Finder, navigate to Applications folder, right-click Adobe Substance 3D Stager.app, select Get Info, and check the Version field under General informationAffected if The version shown is lower than 3.1.8 or shows 3.1.7 or earlier
-
Check version via application menuLaunch Adobe Substance 3D Stager, click the Help menu (or application menu on macOS), select About Adobe Substance 3D Stager, and note the version number displayed in the dialogAffected if The version displayed is lower than 3.1.8 or shows 3.1.7 or earlier
-
Check Windows registry for versionOpen Registry Editor (regedit), navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\, look for an entry named 'Adobe Substance 3D Stager' and check the DisplayVersion valueAffected if The DisplayVersion value is less than 3.1.8 or shows 3.1.7 or earlier
The environment is affected if Adobe Substance 3D Stager is installed with a version lower than 3.1.8 (such as 3.1.7 or earlier).
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 · scoped3.1.8
Update Substance3D Stager to a version newer than 3.1.7 when a patch becomes available. Until then, avoid opening files from untrusted sources.
3.1.8 or later
- Navigate to the Adobe Substance 3D Stager download page on helpx.adobe.com
- Download the latest version of Substance 3D Stager (version 3.1.8 or later)
- Run the installer and follow the on-screen prompts to complete the installation
- Restart any running instances of Substance 3D Stager
- Verify the installed version by checking Help > About in the application menu
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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-2026-27309 — 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-2026-27309 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