CVE-2025-54237
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 read vulnerability that could lead to memory exposure. An attacker could leverage this vulnerability to disclose sensitive information. 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 confidenceAn out-of-bounds read vulnerability in Adobe Substance3D Stager versions 3.1.3 and earlier allows memory exposure through parsing of malicious files. The vulnerability requires user interaction where a victim must open a specially crafted malicious file to trigger the memory disclosure.
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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 Adobe Substance3D Stager installed version on WindowsOpen Control Panel > Programs and Features, locate 'Adobe Substance 3D Stager' in the list, and note the version number in the 'Version' columnAffected if Version displayed is 3.1.3 or earlier, or any version number less than 3.1.4
-
Check Adobe Substance3D Stager installed version on macOSOpen Finder > Applications, right-click 'Adobe Substance 3D Stager.app', select 'Get Info', and read the version number under 'General'Affected if Version displayed is 3.1.3 or earlier, or any version number less than 3.1.4
-
Check version via command line (Windows)Run 'wmic product get name,version' or query registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Adobe Substance3D Stager} for the Version valueAffected if Returned version is 3.1.3 or earlier, or any version number less than 3.1.4
-
Verify the file parsing component is presentConfirm Adobe Substance3D Stager is installed with full file import capabilities by checking that the application launches and can access File > Open menuAffected if The application is installed and functional - the vulnerability exists in the core file parsing which is always enabled by default
You are affected if Adobe Substance3D Stager is installed with any version prior to 3.1.4, as the vulnerability resides in the built-in file parsing functionality that is always active when opening files.
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
Update Substance3D Stager to a patched version when available. Until then, avoid opening files from untrusted sources.
3.1.4
- 1. Close any running instances of Adobe Substance 3D Stager
- 2. Update Adobe Substance 3D Stager to version 3.1.4 or later via the Adobe Creative Cloud desktop application or Adobe website
- 3. After installation, verify the version number in the application (typically found in Help > About)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54237 — 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-54237 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