Code execution via malicious file parsing
Published Mar 10, 2026 · Updated Mar 10, 2026
Out-of-bounds write in Adobe Substance 3D Stager 3.1.7 and earlier allows attackers to execute code via a malicious file. Adobe has not disclosed the parser or the precise bounds error that writes beyond allocated memory when the file is processed. Exploitation requires a victim to open the crafted file, and resulting code runs in the context of the current user.
Summary
What happened
Out-of-bounds write in Adobe Substance 3D Stager 3.1.7 and earlier allows attackers to execute code via a malicious file. Adobe has not disclosed the parser or the precise bounds error that writes beyond allocated memory when the file is processed. Exploitation requires a victim to open the crafted file, and resulting code runs in the context of the current user.
The record
- CVE
- CVE-2026-27274
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- Adobe
- Product
- Substance 3D Stager
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2026CVE publishedPublication date reported by the CVE source.
- Mar 10, 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 <=3.1.7
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