CVE-2025-24451
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 - Painter versions 10.1.2 and earlier are affected by an out-of-bounds write 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.
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 Painter versions 10.1.2 and earlier contain an out-of-bounds write vulnerability during file parsing. When a victim opens a maliciously crafted file, the vulnerability allows an attacker to overwrite memory boundaries and execute arbitrary code with the privileges 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< 11.0.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
- 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 Painter is installedCheck for the application in the system: look for 'Adobe Substance 3D Painter' in Program Files (Windows) or /Applications (Mac), or search for the executable file named 'Adobe Substance 3D Painter.exe' (Windows) or 'Substance 3D Painter.app' (Mac)Affected if The application is present on the system
-
Determine the installed version numberOpen Substance 3D Painter, then go to Help > About (or press F1) to display the version dialog, or right-click the executable file in File Explorer/Finder and select Properties > Details to view the Product VersionAffected if Unable to retrieve a version number (indicates potential incomplete installation)
-
Compare installed version against affected rangeCheck if the installed version is less than 11.0.0. If the version begins with 10.x (such as 10.0.0 through 10.1.2, or any 10.x release) or is any earlier major version, the installation is within the affected rangeAffected if Installed version is 10.x or earlier (any version number where the major version is less than 11)
The environment is affected if Adobe Substance 3D Painter is installed and the running version is anything below 11.0.0, since the out-of-bounds write flaw exists in all versions prior to the 11.0.0 release.
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 · scoped11.0.0
Update Substance3D Painter to version 10.1.3 or later. Avoid opening files from untrusted sources.
11.0.0
- Check the current version of Adobe Substance 3D Painter by opening the application and navigating to Help > About, or checking in the Creative Cloud desktop app
- Open the Creative Cloud desktop application or navigate to helpx.adobe.com to download the latest version
- Update Adobe Substance 3D Painter to version 11.0.0 or later via the Creative Cloud app or by downloading the installer directly
- Follow the on-screen prompts to complete the installation
- Restart Adobe Substance 3D Painter after the update completes
- Verify the installed version is 11.0.0 or later by checking 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-24451 — 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-24451 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