Code execution via malicious file heap overflow
Published Aug 25, 2026 · Updated Aug 27, 2026
Heap-based buffer overflow in Adobe Substance 3D Sampler 6.0.1 and earlier allows attackers to execute code via a malicious file. Adobe has not disclosed the affected parser, file format, or the specific operation that overruns the heap buffer. Exploitation requires the current user to open the file, and resulting code runs in that user's context.
Summary
What happened
Heap-based buffer overflow in Adobe Substance 3D Sampler 6.0.1 and earlier allows attackers to execute code via a malicious file. Adobe has not disclosed the affected parser, file format, or the specific operation that overruns the heap buffer. Exploitation requires the current user to open the file, and resulting code runs in that user's context.
The record
- CVE
- CVE-2026-48424
- Published
- Aug 25, 2026
- Updated
- Aug 27, 2026
- Vendor
- Adobe
- Product
- Adobe Substance 3D Sampler
- Classifications
- CWE-122, T1203, T1204.002
- 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 <=6.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.
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