OpenSSL · OpenSSL · published 2026-06-09
CVE-2026-34182CMS AuthEnvelopedData Processing May Accept Forged Messages
This month EPSS 1.1% with high severity (CVSS 9.1).
CVE-2026-34182 is not known to be exploited in the wild. EPSS estimates a 1.1% chance of exploitation in the next 30 days, higher than 65% of all CVEs. This OpenSSL vulnerability: CVSS 9.1 (v3.1), attacks can be automated. Fixed upstream in OpenSSL 4.0.1, 3.6.3, 3.5.7, 3.4.6 (+3 more). Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in OpenSSL 4.0.1, 3.6.3, 3.5.7, 3.4.6, 3.0.21, 1.1.1zh, 1.0.2zq.
Patch events
Crypto libraryOpenSSL
OpenSSL security fixes: 18 CVEs
Upgrade to
4.0.13.6.33.5.73.4.63.0.211.1.1zh1.0.2zqWhy: CVE-2026-34182: EPSS 1.1% with high severity (CVSS 9.1).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 1.1% (65th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.1 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- OpenSSL OpenSSL
4.0.0to before4.0.1(affected)3.6.0to before3.6.3(affected)3.5.0to before3.5.7(affected)3.4.0to before3.4.6(affected)3.0.0to before3.0.21(affected)
Description (from the CVE record)#
Issue Summary: Cryptographic Message Services (CMS) processing fails to perform sufficient input validation on the cipher and tag length fields of AuthEnvelopedData containers, leading to various potential compromises. Impact Summary: Attackers making use of these vulnerabilities may achieve key-equivalent functionality for a given CMS recipient and/or bypass integrity validation for a given message. In one use case, an attacker may send a CMS message containing AuthEnvelopedData with the cipher specified as a non-AEAD cipher. OpenSSL erroneously allows this selection, and attempts to decrypt and validate the message. An on-path attacker who captures one legitimate AES-GCM AuthEnvelopedData addressed to the victim can re-emit it with the recipientInfos set left byte-for-byte intact, so the victim's private key still unwraps the genuine CEK (the content-encryption key), but with the inner OID rewritten to AES-256-OFB (Output Feedback Mode, an unauthenticated keystream mode) and with an attacker-chosen IV and ciphertext. The victim initializes AES-256-OFB under the real CEK, never consults the MAC field, and CMS_decrypt() returns success. If the application under attack responds to the attacker with any indicator showing success or failure of the decryption effort, it is possible for the attacker to use this as an oracle to obtain key equivalent functionality for the CEK used for the chosen recipient of the message. In another use case, an attacker can reduce the tag length of the chosen AEAD cipher for a given AuthEnvelopedData container to be a single byte long, allowing an attacker to brute force CMS decryption, producing an integrity bypass for applications that trust CMS_decrypt() to reject modified content. The FIPS modules are not affected by this issue.
Quoted from the CVE Program record.