CVE-2025-24450
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 · moderate confidenceA out-of-bounds write vulnerability in Adobe Substance3D Painter versions 10.1.2 and earlier allows writing data beyond allocated memory boundaries. Successful exploitation requires a user to open a malicious file, which can result in arbitrary code execution 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 installedOn Windows, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Substance 3D Painter or look in C:\Program Files\Adobe\Adobe Substance 3D Painter for the application folderAffected if The application is present on the system
-
Determine the installed version numberOpen Adobe Substance 3D Painter, go to Help > About, or check the version in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Substance 3D Painter\InstalledVersionAffected if The version displayed is earlier than 11.0.0
-
Compare version against affected rangeCompare your installed version (e.g., 10.x.x) to the affected range of 10.1.2 and earlier, which corresponds to versions < 11.0.0Affected if Your installed version is 10.1.2 or any 10.x release below 11.0.0
-
Assess file opening behaviorDetermine whether the user routinely opens .sbsar or other Substance files from untrusted or unknown sources, as exploitation requires opening a malicious fileAffected if Users with vulnerable versions routinely open files from untrusted sources
You are affected if Adobe Substance 3D Painter version 10.1.2 or earlier (below 11.0.0) is installed and 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 · scoped11.0.0
Update Substance3D Painter to a version newer than 10.1.2. Avoid opening untrusted or unexpected files from unknown sources.
Substance 3D Painter 11.0.0 or later
- Verify current version of Adobe Substance 3D Painter by opening the application and checking Help > About
- Close any running instances of Substance 3D Painter
- Download Adobe Substance 3D Painter version 11.0.0 or later from the official Adobe website (helpx.adobe.com)
- Run the installer and follow the on-screen prompts to complete the upgrade
- Launch the updated application and confirm the version shows 11.0.0 or later via Help > About
- Ensure all project files are backed up before opening any untrusted files in the future
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24450 — 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-24450 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