CVE-2025-54203
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 - Modeler versions 1.22.0 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. 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 confidenceAdobe Substance3D Modeler versions 1.22.0 and earlier contain an out-of-bounds read vulnerability in file parsing logic. When a victim opens a specially crafted malicious file, the application reads memory beyond allocated buffer boundaries, potentially exposing sensitive data from the process memory space.
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< 1.22.2CVSS 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.
-
Verify Adobe Substance3D Modeler is installedCheck for the application in the system. On Windows, look in Program Files/Adobe/ or check the Start Menu. On macOS, look in /Applications/ for 'Substance 3D Modeler'. Use command: 'where substance 3d modeler' (Windows) or 'ls /Applications/ | grep -i substance' (macOS).Affected if The application is not found on the system, then the CVE does not apply.
-
Determine the installed version numberOpen Adobe Substance3D Modeler, then access Help > About (or the application menu on macOS) to display the version. Alternatively, check the Windows registry at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Substance3DModeler for Version, or on macOS inspect the app bundle info.plist file.Affected if Unable to retrieve a version number means the version cannot be verified against the affected range.
-
Compare version against the affected rangeIf version is obtained, verify if it is less than 1.22.2. The affected versions are 1.22.0 and all earlier versions (any version < 1.22.2).Affected if Version is less than 1.22.2 (for example, 1.22.0, 1.21.x, 1.20.x). Version 1.22.2 and later are not affected.
-
Assess file processing exposureDetermine if the application is used to open files from external or untrusted sources, as the vulnerability is triggered during file parsing when a specially crafted file is opened.Affected if The application processes files from untrusted sources and the version is in the affected range, the out-of-bounds read can be triggered.
A system is affected if Adobe Substance3D Modeler is installed with a version less than 1.22.2 and the application is used to open files, including potentially untrusted ones.
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 · scoped1.22.2
Apply the vendor-supplied patch or update to Adobe Substance3D Modeler to a version later than 1.22.0. Until a patch is available, avoid opening files from untrusted sources.
Substance 3D Modeler version 1.22.2 or later
- Navigate to the Adobe Substance 3D Modeler application or the Adobe Creative Cloud desktop application
- Check the current installed version of Substance 3D Modeler
- Update to version 1.22.2 or later through the Adobe Creative Cloud desktop application or by downloading from the official Adobe website
- Verify the update was successful by confirming the version number after updating
- Ensure users are instructed not to open untrusted or malicious 3D model files to mitigate the user interaction requirement for exploitation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54203 — 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-54203 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