dbcve.org
Substance 3d StagerApplication · Adobe

CVE-2025-43549

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 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 · moderate confidence

A Use After Free vulnerability in Substance3D Stager versions 3.1.1 and earlier allows arbitrary code execution when a victim opens a malicious file. The vulnerability stems from the application attempting to access memory that has already been freed, potentially allowing an attacker to control execution flow.

MitigationUpgrade Substance3D Stager to a version newer than 3.1.1 when a patch becomes available, and avoid opening untrusted or unexpected 3D scene files until the update 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.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. Check if Adobe Substance3D Stager is installed
    On Windows, check for the presence of the application in Program Files (typically C:\Program Files\Adobe\Adobe Substance 3D Stager) or look for the application in the Start Menu. On macOS, check /Applications for Adobe Substance 3D Stager.app.
    Affected if The application is installed on the system.
  2. Determine the installed version number
    On Windows, right-click the application executable or look in Add/Remove Programs for the version. On macOS, right-click the application in Applications and select Get Info to view the version. Alternatively, launch the application and check Help > About Adobe Substance 3D Stager.
    Affected if Unable to determine version indicates potential installation.
  3. Compare your version to the affected range
    The affected versions are any version prior to 3.1.2. Compare the version number you found in step 2 against 3.1.2. Versions 3.1.1 and earlier are affected; version 3.1.2 and later are fixed.
    Affected if Installed version is 3.1.1 or earlier.
  4. Identify file association and usage patterns
    Substance3D Stager opens .gltf, .glb, .fbx, .obj, and other 3D scene file formats. Check if the application is set as the default handler for any 3D file types, or if users commonly receive and open 3D files from external sources.
    Affected if The application handles untrusted or unexpected 3D scene files.

You are affected if Adobe Substance3D Stager version 3.1.1 or earlier is installed and the application is used to open 3D scene files, including potentially untrusted ones.

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

Upgrade Substance3D Stager to a version newer than 3.1.1 when a patch becomes available, and avoid opening untrusted or unexpected 3D scene files until the update is applied.

Recommended fix High confidence

Substance 3D Stager 3.1.2 or later

  1. Ensure you have a backup of your current work and projects
  2. Close any running instances of Substance 3D Stager
  3. Navigate to the official Adobe website or Adobe Creative Cloud desktop application
  4. Locate Substance 3D Stager in your installed applications
  5. Update to version 3.1.2 or later
  6. After updating, verify the installed version by opening the application and checking the version number in the Help > About menu
  7. Exercise caution when opening files from untrusted sources, even after applying the update

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

Fix this in Substance 3d Stager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,700
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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