User-triggered code execution via unbounded digest copy
Published Apr 9, 2026 · Updated Apr 9, 2026
Stack buffer overflow in osslsigncode before 2.12 allows attackers to execute code by inducing verification of a crafted signed file. The PE, MSI, CAB, and script verification handlers copy the SpcIndirectDataContent digest into a 64-byte stack buffer without checking its length. Exploitation requires a user to run osslsigncode verify on an attacker-supplied signed file, allowing stack corruption in that user's process context or a process crash.
Summary
What happened
Stack buffer overflow in osslsigncode before 2.12 allows attackers to execute code by inducing verification of a crafted signed file. The PE, MSI, CAB, and script verification handlers copy the SpcIndirectDataContent digest into a 64-byte stack buffer without checking its length. Exploitation requires a user to run osslsigncode verify on an attacker-supplied signed file, allowing stack corruption in that user's process context or a process crash.
The record
- CVE
- CVE-2026-39853
- Published
- Apr 9, 2026
- Updated
- Apr 9, 2026
- Vendor
- Michał Trojnara
- Product
- osslsigncode
- Classifications
- CWE-20, CWE-121, CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 9, 2026CVE publishedPublication date reported by the CVE source.
- Apr 9, 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=< 2.12
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