Skip to main content
CVE-2026-63072VulnerabilityPublished Updated

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

Affects opensslSource GCVE Database

0

Not known to be exploited · CVSS 7.5 High · fixed in 1.0.1f-1ubuntu2.27+esm16 : patch openssl soon.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.1f-1ubuntu2.27+esm16, 1.0.2g-1ubuntu4.20+esm18, 1.1.1-1ubuntu2.1~18.04.23+esm10 +12
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
Ubuntu 26.10edk2pkg:deb/ubuntu/edk2?arch=source&distro=stonkingOther threatsAffected
  • 2025.11-3ubuntu7 – 2026.05-2ubuntu3
5 affected builds
Fixed in–
Ubuntu 26.10edk2-hwepkg:deb/ubuntu/edk2-hwe?arch=source&distro=stonkingOther threatsAffected
  • 2025.11-3ubuntu8 – 2026.05-2ubuntu3
5 affected builds
Fixed in–
Ubuntu 26.04 LTSedk2pkg:deb/ubuntu/edk2?arch=source&distro=resoluteOther threatsAffected
  • <2025.11-3ubuntu7.3
Fixed in
  • 2025.11-3ubuntu7.3
Ubuntu 26.04 LTSedk2-hwepkg:deb/ubuntu/edk2-hwe?arch=source&distro=resoluteOther threatsAffected
  • =2025.11-3ubuntu6
  • =2025.11-3ubuntu8
  • =2025.11-3ubuntu8.2
Fixed in–
Ubuntu 26.04 LTSopensslpkg:deb/ubuntu/openssl?arch=source&distro=resoluteOther threatsAffected
  • <3.5.5-1ubuntu3.4
Fixed in
  • 3.5.5-1ubuntu3.4
Ubuntu 24.04 LTSedk2pkg:deb/ubuntu/edk2?arch=source&distro=nobleOther threatsAffected
  • <2024.02-2ubuntu0.10
Fixed in
  • 2024.02-2ubuntu0.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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.

References

Community reviews

Loading reviews…