Microsoft · Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU
Affects MicrosoftSource GCVE Database
Not known to be exploited · fixed in 4.1.1 : update Microsoft when convenient.
Data as of 19 Nov 2026, 09:26 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 4.1.1, 4.0.4, 3.5.10
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade OpenSSL to 4.1.1, 4.0.4 or 3.5.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
Description
A vulnerability in Microsoft product version 4.0 involves excessive CPU consumption when verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled. This issue may lead to performance degradation during signature verification processes.