PoC Monitor
← All CVEs
CVE-2026-63072published 25 Aug 2026 12:59 UTCData: JSON · API

OpenSSL

Heap Buffer Overflow in CMS Key Unwrapping

Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write. Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the unwrap key is derived from the recipient's private operation (ECDH key agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure. The write is a fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the worst case so a failed unwrap cannot write past the allocation. FIPS impact: no As the CMS code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.

First public PoC 21 hafter publication · 26 Aug 2026
Public PoCs33 on GitHub
CVSS7.5high · scored by CISA ADP · CWE-787
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

OpenSSL OpenSSL
  • >= 4.0.0, < 4.0.2
  • >= 3.6.0, < 3.6.4
  • >= 3.5.0, < 3.5.8
  • >= 3.4.0, < 3.4.7
  • >= 3.0.0, < 3.0.22
  • >= 1.1.1, < 1.1.1zi

Fixed in 4.0.2, 3.6.4, 3.5.8, 3.4.7, 3.0.22, 1.1.1zi

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published25 Aug 2026 · t = 0First public PoC26 Aug 2026 · t+21h

First public PoC 21 h after publication; not in CISA KEV. First PoC: 0xBlackash/CVE-2026-63072 (created 26 Aug 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

3 PoCs

PoCs 3
RepositoryCreatedStarsAssessment
0xBlackash/CVE-2026-63072 26 Aug 2026 +21 h 0 PoC via PoC Index
0xredash/CVE-2026-63072 26 Aug 2026 +21 h 0 PoC via PoC Index
ashrafzaryouh/CVE-2026-63072 26 Aug 2026 +21 h 0 PoC via PoC Index

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.