CVE-2025-54222
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.3 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.3 and earlier contain an out-of-bounds write vulnerability in file parsing logic. When a user opens a specially crafted malicious file, the application writes data beyond allocated memory boundaries, potentially allowing 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.4CVSS 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.
-
Check installed version via Windows Programs and FeaturesOpen Control Panel > Programs and Features, locate Adobe Substance 3D Stager in the list, and note the version number shown in the Version columnAffected if The displayed version is 3.1.3 or earlier, or if no version number is visible but the application appears to be an older release
-
Check application executable version propertiesNavigate to the installation directory (typically C:\Program Files\Adobe\Adobe Substance 3D Stager), right-click the Stager.exe file, select Properties, and examine the Details tab for the Product versionAffected if The product version listed is 3.1.3 or any version lower than 3.1.4
-
Verify via Adobe Creative Cloud desktop appOpen the Adobe Creative Cloud application, go to the Apps or Installed apps section, find Adobe Substance 3D Stager, and check the version number displayedAffected if The listed version is 3.1.3 or earlier
-
Confirm file parsing feature usageDetermine whether the application has been used to open or import 3D model files, scene files, or other content from external sourcesAffected if The application has been used to open files, particularly from untrusted or unknown sources, and the installed version is vulnerable
If Adobe Substance 3D Stager version 3.1.3 or earlier is installed, the environment is affected by this out-of-bounds write vulnerability in file parsing.
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.4
Upgrade Substance3D Stager to a version newer than 3.1.3. Until patched, avoid opening files from untrusted sources.
Substance 3D Stager 3.1.4
- Check current version of Substance 3D Stager by opening the application and navigating to Help > About (or the application's version information)
- Download Substance 3D Stager version 3.1.4 or later from the official Adobe website (helpx.adobe.com or adobe.com)
- Close any running instances of Substance 3D Stager
- Run the installer for version 3.1.4 and follow the on-screen prompts to complete the installation
- Verify the update was successful by checking Help > About shows version 3.1.4 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54222 — 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-2025-54222 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