CVE-2025-27180
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.15.0 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 · moderate confidenceSubstance3D Modeler versions 1.15.0 and earlier contain an out-of-bounds read vulnerability that allows reading memory beyond allocated buffers. This can expose sensitive memory contents, including pointers and addresses that can be leveraged to defeat ASLR. Exploitation requires user interaction—specifically, the victim must open a maliciously crafted file.
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.15.0CVSS 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.
-
Confirm Adobe Substance 3D Modeler is installedLook for the application in the system: On Windows check C:\Program Files\Adobe\Adobe Substance 3D Modeler\ or the Start Menu. On macOS check /Applications/Adobe Substance 3D Modeler.appAffected if The application is present on the system
-
Identify the installed version of ModelerOpen Modeler and navigate to Help > About, or check the version in the application properties. On Windows, you may also check Add/Remove Programs or the executable's properties. On macOS, right-click the app bundle and select Get Info to view the version.Affected if The displayed version is any version prior to 1.15.0 (e.g., 1.14.x, 1.13.x, etc.)
-
Verify the version is within the affected rangeCompare your installed version number against the affected range: versions less than 1.15.0 are vulnerable. Note that version 1.15.0 itself may also be affected if the fix was released in a later patch.Affected if The installed version is 1.15.0 or any earlier release (1.x.x where x < 15)
-
Determine if Modeler is used to open external filesSubstance3D Modeler is a 3D modeling tool that loads project files. Check whether you or users in your environment open .s3d, .obj, .fbx, or other 3D file formats with this application.Affected if Users open files from untrusted or unknown sources in Modeler, as exploitation requires opening a maliciously crafted file
You are affected if Adobe Substance 3D Modeler is installed and the installed version is 1.15.0 or earlier, especially if users open 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.15.0
Update Substance3D Modeler to a version newer than 1.15.0 once the vendor releases the patch. Until then, refrain from opening files from untrusted sources in Modeler.
Substance 3D Modeler 1.15.0 or later
- Open Adobe Creative Cloud desktop application or navigate to Adobe's Substance 3D Modeler product page
- Check current installed version of Substance 3D Modeler (typically via Help > About in the application)
- Update Substance 3D Modeler to version 1.15.0 or later through the Adobe Creative Cloud app or by downloading from Adobe's website
- Restart the application if prompted
- Verify the installed version is 1.15.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27180 — 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-27180 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