Code execution via heap buffer overflow
Published Aug 25, 2026 · Updated Aug 27, 2026
Heap-based buffer overflow in Adobe Substance 3D Designer 16.0.4 and earlier allows attackers to execute code through a malicious file. Adobe identifies the weakness but has not disclosed the affected parser, file field, or heap copy operation that mishandles the file. Exploitation requires a victim to open the file and runs code only in the current user's context, allowing compromise of that user's data and application access.
Summary
What happened
Heap-based buffer overflow in Adobe Substance 3D Designer 16.0.4 and earlier allows attackers to execute code through a malicious file. Adobe identifies the weakness but has not disclosed the affected parser, file field, or heap copy operation that mishandles the file. Exploitation requires a victim to open the file and runs code only in the current user's context, allowing compromise of that user's data and application access.
The record
- CVE
- CVE-2026-48430
- Published
- Aug 25, 2026
- Updated
- Aug 27, 2026
- Vendor
- Adobe
- Product
- Adobe Substance 3D Designer
- Classifications
- CWE-122, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 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 <=16.0.4
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