CVE-2026-63072: Heap Buffer Overflow in CMS Key Unwrapping
Noroxi assessment
Priority: Monitor (action score 30/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.91% (FIRST EPSS); higher than 60.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: OpenSSL OpenSSL 3.0.22, 3.4.7, 3.5.8; azl3 edk2 20240524git3e722403cd16-18 on Azure Linux 3.0 20240524git3e722403cd16-19; azl3 edk2 20240524git3e722403cd16-20 on Azure Linux 3.0 20240524git3e722403cd16-19.
Low priority for now. Upgrade to OpenSSL OpenSSL 3.0.22, 3.4.7, 3.5.8; azl3 edk2 20240524git3e722403cd16-18 on Azure Linux 3.0 20240524git3e722403cd16-19; azl3 edk2 20240524git3e722403cd16-20 on Azure Linux 3.0 20240524git3e722403cd16-19 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2026-13717
- EUVD-2026-65482
- ALSA-2026:67154
- ALSA-2026:67165
- ALSA-2026:80514
- ALSA-2026:85968
- openSUSE-SU-2026:11623-1
- openSUSE-SU-2026:21744-1
- RHSA-2026:59635
- RHSA-2026:59641
- RHSA-2026:67154
- RHSA-2026:67165
- RHSA-2026:80514
- RHSA-2026:85249
- RLSA-2026:67154
- RLSA-2026:67165
- RLSA-2026:80514
- SUSE-SU-2026:23463-1
- SUSE-SU-2026:23473-1
- SUSE-SU-2026:23512-1
- Published
- Aug 25, 2026
- Updated
- Sep 11, 2026
- EPSS
- 0.9% · 60th percentile
- CWE
- CWE-787
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Check your server's TLS configurationRun the SSL check
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
Check your server's TLS configuration
The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openssl openssl3.0.0 and later · before 3.0.22
- openssl openssl3.4.0 and later · before 3.4.7
- openssl openssl3.5.0 and later · before 3.5.8
- openssl openssl3.6.0 and later · before 3.6.4
- openssl openssl4.0.0 and later · before 4.0.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.
OpenSSL OpenSSL
- 4.0.0 and later · before 4.0.2affected · semver
- 3.6.0 and later · before 3.6.4affected · semver
- 3.5.0 and later · before 3.5.8affected · semver
- 3.4.0 and later · before 3.4.7affected · semver
- 3.0.0 and later · before 3.0.22affected · semver
- 1.1.1 and later · before 1.1.1ziaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | openssl | before 1:3.5.8-1.el10_2.alma.1 | 1:3.5.8-1.el10_2.alma.1 |
| AlmaLinux:10 | openssl-devel | before 1:3.5.8-1.el10_2.alma.1 | 1:3.5.8-1.el10_2.alma.1 |
| AlmaLinux:10 | openssl-libs | before 1:3.5.8-1.el10_2.alma.1 | 1:3.5.8-1.el10_2.alma.1 |
| AlmaLinux:10 | openssl-perl | before 1:3.5.8-1.el10_2.alma.1 | 1:3.5.8-1.el10_2.alma.1 |
| AlmaLinux:8 | openssl | before 1:1.1.1k-18.el8_6 | 1:1.1.1k-18.el8_6 |
| AlmaLinux:8 | openssl-devel | before 1:1.1.1k-18.el8_6 | 1:1.1.1k-18.el8_6 |
| AlmaLinux:8 | openssl-libs | before 1:1.1.1k-18.el8_6 | 1:1.1.1k-18.el8_6 |
| AlmaLinux:8 | openssl-perl | before 1:1.1.1k-18.el8_6 | 1:1.1.1k-18.el8_6 |
| AlmaLinux:9 | compat-openssl11 | before 1:1.1.1k-5.el9_8.6 | 1:1.1.1k-5.el9_8.6 |
| AlmaLinux:9 | openssl | before 1:3.5.8-1.el9_8 | 1:3.5.8-1.el9_8 |
| AlmaLinux:9 | openssl-devel | before 1:3.5.8-1.el9_8 | 1:3.5.8-1.el9_8 |
| AlmaLinux:9 | openssl-libs | before 1:3.5.8-1.el9_8 | 1:3.5.8-1.el9_8 |
| AlmaLinux:9 | openssl-perl | before 1:3.5.8-1.el9_8 | 1:3.5.8-1.el9_8 |
| Alpine:v3.21 | openssl | from 3.0.0 · before 3.3.7-r1 | 3.3.7-r1 |
| Alpine:v3.22 | openssl | from 3.0.0 · before 3.5.8-r0 | 3.5.8-r0 |
| Debian:12 | openssl | before 3.0.22-1~deb12u1 | 3.0.22-1~deb12u1 |
| Debian:13 | openssl | before 3.5.7-1~deb13u2 | 3.5.7-1~deb13u2 |
| Debian:14 | openssl | before 3.6.4-1 | 3.6.4-1 |
| openSUSE:Leap 16.0 | openssl-3 | before 3.5.0-160000.10.1 | 3.5.0-160000.10.1 |
| openSUSE:Tumbleweed | openssl-3 | before 3.5.3-8.1 | 3.5.3-8.1 |
| Red Hat:enterprise_linux:10.2 | openssl | before 1:3.5.8-1.el10_2 | 1:3.5.8-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | openssl-debuginfo | before 1:3.5.8-1.el10_2 | 1:3.5.8-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | openssl-debugsource | before 1:3.5.8-1.el10_2 | 1:3.5.8-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | openssl-devel | before 1:3.5.8-1.el10_2 | 1:3.5.8-1.el10_2 |
+52
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows…KEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code…65This week
Published before and after this one in the same product
- ← EarlierCVE-2026-18798Aug 25, 2026 · QUIC Server May Trigger Double Free When Processing INITIAL Packet31Monitor
- ← EarlierCVE-2026-54874Aug 25, 2026 · Excessive Memory Use Buffering DTLS Records for a Future Epoch30Monitor
- Later →CVE-2026-63073Aug 25, 2026 · Untrusted Sender DN Used as Format String in CMP Response Validation39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| OpenSSL OpenSSL | 3.0.22 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.4.7 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.5.8 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.6.4 | Vendor (CNA) |
| OpenSSL OpenSSL | 4.0.2 | Vendor (CNA) |
| azl3 edk2 20240524git3e722403cd16-18 on Azure Linux 3.0 | 20240524git3e722403cd16-19 | Microsoft (MSRC) |
| azl3 edk2 20240524git3e722403cd16-20 on Azure Linux 3.0 | 20240524git3e722403cd16-19 | Microsoft (MSRC) |
| azl3 openssl 3.3.7-4 on Azure Linux 3.0 | 3.3.7-6 | Microsoft (MSRC) |
| azl3 openssl 3.3.7-6 on Azure Linux 3.0 | 3.3.7-6 | Microsoft (MSRC) |
| almalinux:compat-openssl11 | 1:1.1.1k-5.el9_8.6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl | 1:3.5.8-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:openssl-devel | 1:3.5.8-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:openssl-libs | 1:3.5.8-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:openssl-perl | 1:3.5.8-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| alpine:openssl | 3.3.7-r1 · Alpine:v3.21 | Package registry (OSV) |
| debian:openssl | 3.0.22-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:openssl-3 | 3.5.3-8.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:openssl | 0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-config-fips | 0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-debuginfo | 1:3.5.8-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl-devel | 0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-devel-engine | 0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-fips-provider-upstream | 0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-libs | 0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-perl | 0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3 | 0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3-devel | 0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3-devel-engine | 0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3-libs | 0:3.5.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| rocky linux:compat-openssl11 | 1:1.1.1k-5.el9_8.6 · Rocky Linux:9 | Package registry (OSV) |
+6
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-08-26 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+1 d
- TodayNov 11, 2026+78 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Bhabani Sankar Dasreporter
- Daniel Kubecremediation developer
- Filipe Casal(TrailBits)reporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-15467210 days apartStack buffer overflow in CMS (Auth)EnvelopedData parsing57Plan
- CVE-2026-31789140 days apartHeap Buffer Overflow in Hexadecimal Conversion39Monitor
- CVE-2026-738377 days apartPossible Heap Buffer Overflow in ASN.1 Multibyte String Conversion32Monitor
- CVE-2026-7289735 days apartOut-of-Bounds Access After SSL_set_SSL_CTX() During a Handshake30Monitor
- CVE-2025-69419210 days apartOut of bounds write in PKCS12_get_friendlyname() UTF-8 conversion29Monitor
- CVE-2025-68160210 days apartHeap out-of-bounds write in BIO_f_linebuffer on short writes18Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- github.com/openssl/openssl/commit/87784ad619af36b8807c2044b3940006fccc1e42
- github.com/openssl/openssl/commit/9530a5fd1aacaeccdced4478ea2340a480613335
- github.com/openssl/openssl/commit/9ec2f6d2ae2bcad907cf7ee38584855bafe4979a
- github.com/openssl/openssl/commit/a0c8ec557d9cac078f032d76cdf684fe743eb382
- openssl-library.org/news/secadv/20260825.txt
Vendor advisories and official records. Exploit/PoC links are deliberately left out.