CVE-2025-54259
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 Integer Overflow or Wraparound 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. 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 versions 1.22.2 and earlier contain an integer overflow vulnerability in file parsing logic. When a user opens a specially crafted malicious 3D model file, the integer overflow can be triggered during parsing, leading to heap corruption and ultimately 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.
-
Confirm Substance 3D Modeler installationCheck if Adobe Substance 3D Modeler is installed on the system. On Windows, look in Program Files or the Adobe Creative Cloud folder. On macOS, check /Applications for 'Adobe Substance 3D Modeler'.Affected if If the application is present on the system, proceed to version check.
-
Identify installed version numberOpen Substance 3D Modeler and navigate to Help > About Adobe Substance 3D Modeler, or check the version in the application properties via the system installer. On Windows, right-click the executable and select Properties > Details. On macOS, right-click the app > Get Info.Affected if Version information is needed to determine vulnerability status.
-
Compare version to affected rangeCompare your installed version to the vulnerable range: any version below 1.22.4 is affected. Version 1.22.2 and earlier are specifically listed as vulnerable.Affected if If the installed version is less than 1.22.4, the environment is within the affected version range.
-
Assess file handling exposureDetermine if users routinely import or open 3D model files from external or untrusted sources. Check for recent model file imports or user workflows involving downloaded or received 3D files.Affected if If users open 3D model files from untrusted sources, the exploitation precondition is present.
The environment is affected if Substance 3D Modeler version 1.22.2 or earlier (below 1.22.4) is installed AND users may open model files from untrusted sources.
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 not open files from untrusted sources. Organizations should update Substance3D Modeler to a version beyond 1.22.2 once the vendor releases a patch addressing this vulnerability.
1.22.4
- Close any running instances of Adobe Substance 3D Modeler
- Navigate to the official Adobe Substance 3D Modeler download page at helpx.adobe.com
- Download version 1.22.4 (or the latest available version) for your operating system
- Run the installer and follow the on-screen prompts to complete the update
- Launch Substance 3D Modeler and verify the version by checking Help > About to confirm version 1.22.4 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54259 — 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-54259 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