dbcve.org
Substance 3d StagerApplication · Adobe

CVE-2026-27275

HIGH · 7.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 3.1.8 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Substance3D - 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 confidence

Substance3D Stager versions 3.1.7 and earlier contain an out-of-bounds write vulnerability that allows arbitrary code execution when a user opens a maliciously crafted file. The vulnerability exists in file parsing logic and enables memory corruption that can be leveraged for code execution in the context of the current user.

MitigationUpgrade Substance3D Stager to a version newer than 3.1.7 and exercise caution when opening files from untrusted sources until the patch is applied.

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
Substance 3d StagerApplication
Affected:< 3.1.8

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Substance 3D Stager installation
    Search for the application executable (typically named 'Substance 3D Stager.exe' on Windows or found in the Applications folder on macOS)
    Affected if The application is installed on the system
  2. Determine the installed version
    Right-click the executable and select Properties, then view the Details tab for version information. On macOS, right-click the app, select Get Info, and check the Version field. Alternatively, check the application's Help > About menu.
    Affected if The version displayed is 3.1.7 or earlier, or shows a version lower than 3.1.8
  3. Verify the version against the affected range
    Compare the installed version number to the affected range: any version below 3.1.8 is vulnerable
    Affected if The installed version is 3.1.7, 3.1.6, 3.1.5, or any earlier version, or if the version cannot be determined but the software is present
  4. Confirm file parsing is accessible
    The vulnerability is triggered when opening maliciously crafted files - verify that the application's file import functionality is available and operational
    Affected if The software can open or import 3D scene files (such as .obj, .fbx, or native .stager files)

A user is affected if Adobe Substance 3D Stager is installed with any version lower than 3.1.8, as the out-of-bounds write vulnerability in the file parsing logic can be triggered by opening a specially crafted malicious file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.1.8 or later
Fixed in 3.1.8
Interim mitigation

Upgrade Substance3D Stager to a version newer than 3.1.7 and exercise caution when opening files from untrusted sources until the patch is applied.

Recommended fix High confidence

3.1.8

  1. Open Adobe Substance 3D Stager
  2. Navigate to Help > Check for Updates to see the current installed version
  3. If running version 3.1.7 or earlier, download Substance 3D Stager version 3.1.8 from the official Adobe website (helpx.adobe.com)
  4. Run the installer and follow the prompts to complete the upgrade
  5. After installation, verify the version is 3.1.8 by checking Help > About in the application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Substance 3d Stager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27275 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27275 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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