Arbitrary code execution via out-of-bounds write
Published Jul 8, 2025 · Updated Jul 8, 2025
Out-of-bounds write in Adobe Substance 3D Designer 14.1 and earlier allows attackers to execute code via a malicious file. Adobe identifies the fault only as an out-of-bounds write during malicious-file handling and does not disclose the affected parser, file format, or faulty bounds operation. A victim must open the crafted file, after which code executes with the victim's current-user privileges and can compromise confidentiality, integrity, and availability.
Summary
What happened
Out-of-bounds write in Adobe Substance 3D Designer 14.1 and earlier allows attackers to execute code via a malicious file. Adobe identifies the fault only as an out-of-bounds write during malicious-file handling and does not disclose the affected parser, file format, or faulty bounds operation. A victim must open the crafted file, after which code executes with the victim's current-user privileges and can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2025-21164
- Published
- Jul 8, 2025
- Updated
- Jul 8, 2025
- Vendor
- Adobe
- Product
- Substance 3D Designer
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2025CVE publishedPublication date reported by the CVE source.
- Jul 8, 2025Record 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 <=14.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.
Weakness, pattern, technique
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