CVE-2025-54260
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.2 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file. Scope is unchanged.
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 Modeler contains an out-of-bounds read vulnerability in its file parsing logic. When parsing a specially crafted malicious file, the application reads memory past the end of an allocated buffer. This can be leveraged by an attacker to achieve 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< 1.22.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.
-
Verify Adobe Substance 3D Modeler is installedCheck for the presence of the application. On Windows, look for 'Adobe Substance 3D Modeler' in Program Files or check the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. On macOS, check /Applications for Substance 3D Modeler.app.Affected if The application is installed on the system
-
Determine the installed versionLaunch the application and navigate to Help > About Adobe Substance 3D Modeler, or check the version in the application metadata. On Windows, the version may also be listed in Add/Remove Programs.Affected if The installed version is lower than 1.22.4
-
Confirm file import functionality is accessibleVerify the application can import model files. Launch the app and check if the Open or Import file dialogs are available, or if there are recent files indicating file parsing has been used.Affected if The application supports opening or importing model files from external sources
-
Check for recently opened model filesExamine the application's recent files list (usually in File > Open Recent) or check the user AppData folder for traces of recently parsed model files that could have triggered the vulnerability.Affected if Untrusted model files have been opened with the application
A user is affected if Adobe Substance 3D Modeler is installed with a version lower than 1.22.4 and the file parsing feature has been used to open external model 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 · scoped1.22.4
Users should avoid opening files from untrusted sources. Organizations should deploy the vendor patch when released and consider application segmentation to limit exposure.
1.22.4 or later
- Check the current version of Substance 3D Modeler installed on the system
- Navigate to the Adobe Substance 3D Modeler download page or use the Adobe Creative Cloud desktop application
- Download and install Substance 3D Modeler version 1.22.4 or later
- Verify the installed version matches or exceeds 1.22.4 after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54260 — 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-54260 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