CVE-2026-39853: CWE-121: Stack-based Buffer Overflow in mtrojnar osslsigncode
osslsigncode is a tool that implements Authenticode signing and timestamping. Prior to 2.12, A stack buffer overflow vulnerability exists in osslsigncode in several signature verification paths. During verification of a PKCS#7 signature, the code copies the digest value from a parsed SpcIndirectDataContent structure into a fixed-size stack buffer (mdbuf[EVP_MAX_MD_SIZE], 64 bytes) without validating that the source length fits within the destination buffer. This pattern is present in the verification handlers for PE, MSI, CAB, and script files. An attacker can craft a malicious signed file with an oversized digest field in SpcIndirectDataContent. When a user verifies such a file with osslsigncode verify, the unbounded memcpy can overflow the stack buffer and corrupt adjacent stack state. This vulnerability is fixed in 2.12.
AI Analysis
Technical Summary
osslsigncode, a tool for Authenticode signing and timestamping, contains a stack buffer overflow vulnerability in versions before 2.12. The issue arises because the code copies the digest value from a parsed SpcIndirectDataContent structure into a fixed-size stack buffer (64 bytes) without validating that the source length fits, leading to potential overflow. This vulnerability is present in multiple signature verification paths including PE, MSI, CAB, and script files. An attacker can exploit this by crafting a malicious signed file with an oversized digest field, causing stack corruption during verification. The vulnerability is tracked as CVE-2026-39853 and has a CVSS 3.1 score of 7.8 (high severity). The issue is fixed in osslsigncode version 2.12.
Potential Impact
Successful exploitation can lead to stack corruption, potentially allowing an attacker to execute arbitrary code, cause denial of service, or compromise the integrity and availability of the verification process. The vulnerability affects local users who run osslsigncode verify on crafted malicious files. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade osslsigncode to version 2.12 or later, where this vulnerability is fixed. Since no official patch links or vendor advisories are provided, verify the upgrade from the official mtrojnar osslsigncode source. Avoid verifying untrusted signed files with vulnerable versions until patched.
CVE-2026-39853: CWE-121: Stack-based Buffer Overflow in mtrojnar osslsigncode
Description
osslsigncode is a tool that implements Authenticode signing and timestamping. Prior to 2.12, A stack buffer overflow vulnerability exists in osslsigncode in several signature verification paths. During verification of a PKCS#7 signature, the code copies the digest value from a parsed SpcIndirectDataContent structure into a fixed-size stack buffer (mdbuf[EVP_MAX_MD_SIZE], 64 bytes) without validating that the source length fits within the destination buffer. This pattern is present in the verification handlers for PE, MSI, CAB, and script files. An attacker can craft a malicious signed file with an oversized digest field in SpcIndirectDataContent. When a user verifies such a file with osslsigncode verify, the unbounded memcpy can overflow the stack buffer and corrupt adjacent stack state. This vulnerability is fixed in 2.12.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
osslsigncode, a tool for Authenticode signing and timestamping, contains a stack buffer overflow vulnerability in versions before 2.12. The issue arises because the code copies the digest value from a parsed SpcIndirectDataContent structure into a fixed-size stack buffer (64 bytes) without validating that the source length fits, leading to potential overflow. This vulnerability is present in multiple signature verification paths including PE, MSI, CAB, and script files. An attacker can exploit this by crafting a malicious signed file with an oversized digest field, causing stack corruption during verification. The vulnerability is tracked as CVE-2026-39853 and has a CVSS 3.1 score of 7.8 (high severity). The issue is fixed in osslsigncode version 2.12.
Potential Impact
Successful exploitation can lead to stack corruption, potentially allowing an attacker to execute arbitrary code, cause denial of service, or compromise the integrity and availability of the verification process. The vulnerability affects local users who run osslsigncode verify on crafted malicious files. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade osslsigncode to version 2.12 or later, where this vulnerability is fixed. Since no official patch links or vendor advisories are provided, verify the upgrade from the official mtrojnar osslsigncode source. Avoid verifying untrusted signed files with vulnerable versions until patched.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-07T19:13:20.378Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d7ce5e1cc7ad14dae8f922
Added to database: 4/9/2026, 4:05:50 PM
Last enriched: 4/9/2026, 4:20:44 PM
Last updated: 4/9/2026, 5:06:25 PM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.