Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
High

Out-of-bounds read in OpenSSL CMS password-based decryption

IdentifiersCVE-2026-9076CWE-125· Out-of-bounds Read

CVE-2026-9076 is a low-severity heap out-of-bounds read in OpenSSL's CMS password-based decryption path for RFC 3211 / PWRI key unwrap processing. When OpenSSL processes attacker-supplied CMS data, the attacker can choose the KEK cipher via the PWRI keyEncryptionAlgorithm OID. The vulnerable unwrap logic in kek_unwrap_key() performs the RFC-mandated check-byte test by reading 7 bytes from a heap allocation sized from the wrapped-key length in the message. Although a minimum-length guard exists, it is based on the wrapping cipher block length and is ineffective if the attacker selects a stream-mode cipher rather than a block cipher. In that case, the allocated buffer for the unwrapped key may be too small to contain the expected check bytes, leading to a heap buffer over-read during the unwrap attempt. The issue affects applications that call CMS_decrypt() or CMS_decrypt_set1_password(), including equivalent openssl cms -decrypt -pwri_password usage, on untrusted CMS input. The over-read occurs before password authentication succeeds, so no password knowledge is required to trigger it. The OpenSSL FIPS modules are not affected.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause a process crash and resulting denial of service if the small heap over-read crosses into unmapped memory, such as when the buffer ends at a page boundary and the following page is unmapped. The advisory states there is no information disclosure because the over-read bytes are not returned or otherwise exposed to the attacker. The practical impact is therefore limited to availability loss rather than confidentiality or integrity compromise.

Mitigation

If you can’t patch tonight, do this now.

Do not process untrusted CMS password-based encrypted content through CMS_decrypt() or CMS_decrypt_set1_password() until patched. Reject or strictly gate untrusted CMS inputs, especially PWRI-based encrypted CMS objects where the attacker controls the keyEncryptionAlgorithm OID. Where operationally feasible, avoid the affected password-based CMS decryption path or use unaffected FIPS module deployments, noting that the FIPS modules are not impacted by this issue.

Remediation

Patch, then assume compromise.

Upgrade OpenSSL to a vendor-fixed release that includes the June 9, 2026 security advisory fixes. The provided context indicates fixes were issued in supported branches including OpenSSL 4.0.1, 3.6.3, 3.5.7, 3.4.6, 3.0.21, 1.1.1zh, and 1.0.2zq, and downstream vendors such as Alpine, Debian, FreeBSD, and Microsoft have published corresponding updates. Apply the appropriate package or base-system update for the affected platform and restart dependent services or reboot if required by the vendor.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreebsdFreebsdapplication
OpenSSL Software FoundationOpensslapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity19

Community discussion across Reddit, Mastodon, and other social sources.