Substance 3d StagerApplication · Adobe

CVE-2025-64531

HIGH · 7.8 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 3.1.6 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.5 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 confidence

A Use After Free vulnerability exists in Substance3D Stager versions 3.1.5 and earlier during file parsing. When processing a maliciously crafted file, memory is deallocated but the program continues to use the freed memory pointer, potentially allowing an attacker to control memory layout and achieve arbitrary code execution in the context of the current user.

MitigationUpdate Substance3D Stager to a version newer than 3.1.5 when a patch is released by Adobe. Until then, exercise caution when opening files from untrusted sources.

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

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 installed Adobe Substance 3D Stager version
    Open the application and navigate to Help > About (or check the application properties in your installation directory). Alternatively, on Windows check Add/Remove Programs or the application's info.plist on macOS.
    Affected if The displayed version is 3.1.5 or earlier, or any version lower than 3.1.6
  2. Verify the file parsing functionality is accessible
    Confirm the application can open or import files (the vulnerability triggers during the parsing of crafted files).
    Affected if The application has file import or open capabilities enabled and can process external files.
  3. Confirm the vulnerability trigger condition
    The Use After Free flaw is triggered specifically when processing a maliciously crafted file. Any user who opens untrusted files in Substance 3D Stager is potentially affected.
    Affected if Users open files from untrusted sources in the affected application version.

You are affected if Adobe Substance 3D Stager is installed at version 3.1.5 or earlier (any version below 3.1.6) and the application is used to open or parse files.

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.6 or later
Fixed in 3.1.6
Interim mitigation

Update Substance3D Stager to a version newer than 3.1.5 when a patch is released by Adobe. Until then, exercise caution when opening files from untrusted sources.

Recommended fix High confidence

3.1.6

  1. Open Substance 3D Stager and navigate to Help > About (or check the application version in its preferences) to confirm the current installed version
  2. If running version 3.1.5 or earlier, close the application
  3. Open Adobe Creative Cloud desktop application and navigate to the Apps section
  4. Find Substance 3D Stager in the list of installed apps and click Update to install version 3.1.6
  5. Alternatively, download Substance 3D Stager version 3.1.6 directly from Adobe's official website at helpx.adobe.com
  6. Launch the updated application and verify the version shows 3.1.6

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64531 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