CVE-2026-27279
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 an out-of-bounds write 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 an out-of-bounds write vulnerability that can be triggered by opening a specially crafted malicious file, leading to arbitrary code execution in the context of the current user.
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.
-
Locate Adobe Substance 3D Stager installation directoryCheck common installation paths: %ProgramFiles%\Adobe\Adobe Substance 3D Stager or %ProgramFiles(x86)%\Adobe\Adobe Substance 3D Stager on Windows; /Applications/Adobe Substance 3D Stager on macOSAffected if The application directory exists on the system
-
Find the installed version numberWithin the installation folder, locate the version info file or right-click the executable and select Properties > Details to view the File VersionAffected if A version number is displayed in the file properties
-
Compare version to affected rangeCompare your installed version to the affected range: any version lower than 3.1.8 (including 3.1.7 and earlier) is vulnerableAffected if Installed version is 3.1.7 or any version below 3.1.8
If Adobe Substance 3D Stager is installed and the version is lower than 3.1.8, the environment is affected by this vulnerability.
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. Avoid opening untrusted files from unknown sources until the update is applied.
Substance 3D Stager 3.1.8 or later
- Check the current version of Substance 3D Stager by opening the application and navigating to Help > About (or checking within the application's version information)
- Open the Adobe Creative Cloud desktop application on your system
- Navigate to the 'Apps' section in Creative Cloud
- Find Substance 3D Stager in the list of installed applications
- Click the 'Update' button if an update to version 3.1.8 or later is available
- If no update appears, click the three-dot menu next to the application and select 'Update Now' to force check for updates
- Wait for the download and installation to complete, then restart the application if prompted
- Verify the update was successful by checking the version number again (Help > About)
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-2026-27279 — 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-27279 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