dbcve.org
Substance 3d StagerApplication · Adobe

CVE-2025-43569

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 3.1.2 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.1 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

Out-of-bounds write vulnerability in Substance3D Stager versions 3.1.1 and earlier allows arbitrary code execution when a user opens a malicious file. The vulnerability stems from improper bounds checking during file parsing, enabling memory corruption that can be leveraged for code execution in the current user's context.

MitigationApply vendor patch/upgrade to a version newer than 3.1.1 when available; avoid opening untrusted or unexpected 3D scene files until the update is deployed.

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.2

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. Confirm Adobe Substance 3D Stager is installed
    Check for the application in typical installation locations: Windows: C:\Program Files\Adobe\Adobe Substance 3D Stager or C:\Program Files (x86)\Adobe\Adobe Substance 3D Stager; macOS: /Applications/Adobe Substance 3D Stager. Alternatively, use system package managers or search the installed programs list.
    Affected if The application is found on the system
  2. Identify the installed version
    Windows: Right-click the executable or shortcut, select Properties, then look at the Details tab for File Version. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Adobe\Substance 3D Stager or HKLM\SOFTWARE\WOW6432Node\Adobe\Substance 3D Stager for the Version value. macOS: Right-click the app in Applications, select Get Info, and read the Version field, or run: defaults read /Applications/Adobe\ Substance\ 3D\ Stager.app/Contents/Info CFBundleShortVersionString
    Affected if A version number is returned from the above locations
  3. Compare version against affected range
    Evaluate the identified version number: if it is 3.1.1 or any earlier version (such as 3.1.0, 3.0.x, 2.x, 1.x), the installation is within the affected range. Versions 3.1.2 and later are not affected.
    Affected if The installed version is 3.1.1 or earlier (meaning less than 3.1.2)

The system is affected if Adobe Substance 3D Stager is installed with any version prior to 3.1.2.

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.2 or later
Fixed in 3.1.2
Interim mitigation

Apply vendor patch/upgrade to a version newer than 3.1.1 when available; avoid opening untrusted or unexpected 3D scene files until the update is deployed.

Recommended fix High confidence

Adobe Substance 3D Stager 3.1.2

  1. 1. Close any running instances of Adobe Substance 3D Stager
  2. 2. Back up any existing projects and custom settings if desired
  3. 3. Uninstall the current version of Substance 3D Stager from the system
  4. 4. Navigate to the official Adobe download page at helpx.adobe.com
  5. 5. Download Substance 3D Stager version 3.1.2 or later
  6. 6. Run the installer and follow the on-screen prompts to complete the installation
  7. 7. Verify the installed version by opening Stager and checking Help > About Adobe Substance 3D Stager

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

Fix this in Substance 3d Stager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43569 — 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-2025-43569 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