Code execution via out-of-bounds file write
Published Jun 10, 2025 · Updated Feb 26, 2026
Out-of-bounds write in Adobe Substance 3D Painter 11.0.1 and earlier allows attackers to execute code after a malicious file is opened. Adobe identifies the flaw as an out-of-bounds write but has not disclosed the affected parser, file format, or incorrect bounds operation. A user must open an attacker-supplied file; successful exploitation runs code in that user's context.
Summary
What happened
Out-of-bounds write in Adobe Substance 3D Painter 11.0.1 and earlier allows attackers to execute code after a malicious file is opened. Adobe identifies the flaw as an out-of-bounds write but has not disclosed the affected parser, file format, or incorrect bounds operation. A user must open an attacker-supplied file; successful exploitation runs code in that user's context.
The record
- CVE
- CVE-2025-47108
- Published
- Jun 10, 2025
- Updated
- Feb 26, 2026
- Vendor
- Adobe
- Product
- Substance 3D Painter
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=11.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo