CVE
CVE-2026-34182
OpenSSL · OpenSSL
- First Reported
- Sep 16, 2026
- Latest Reported
- Sep 16, 2026
CVE Enrichment
- CVSS
- 9.1 CRITICAL
- EPSS
- 1.06%
- EPSS Percentile
- 64.69%
- CISA KEV
- Not listed
Description
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.
Technical Details
- CVSS Version
- 3.1
- CNA / NVD Source
- [email protected]
- Published
- 10-Jun-2026 00:17
- Last Modified
- 23-Jul-2026 15:10
- EPSS Date
- 2026-11-09
- CWE
- CWE-354
CVSS Vector
CVSS:3.1 AV:N /
AC:L /
PR:N /
UI:N /
S:U /
C:H /
I:H /
A:N
CNA Products / Version Status
- OpenSSL · OpenSSL
Source: CNA · [email protected]
Default status: unaffected
4.0.0 ≤ version < 4.0.1 — affected (semver)
3.6.0 ≤ version < 3.6.3 — affected (semver)
3.5.0 ≤ version < 3.5.7 — affected (semver)
3.4.0 ≤ version < 3.4.6 — affected (semver)
3.0.0 ≤ version < 3.0.21 — affected (semver)
Affected Products / Versions
- openssl / openssl
Source: NVD CPE · affected
Version / affected range: * · from (inclusive) 3.0.0 · before (exclusive) 3.0.21
cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* - openssl / openssl
Source: NVD CPE · affected
Version / affected range: * · from (inclusive) 3.4.0 · before (exclusive) 3.4.6
cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* - openssl / openssl
Source: NVD CPE · affected
Version / affected range: * · from (inclusive) 3.5.0 · before (exclusive) 3.5.7
cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* - openssl / openssl
Source: NVD CPE · affected
Version / affected range: * · from (inclusive) 3.6.0 · before (exclusive) 3.6.3
cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* - openssl / openssl
Source: NVD CPE · affected
Version / affected range: 4.0.0
cpe:2.3:a:openssl:openssl:4.0.0:-:*:*:*:*:*:*
References
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.
Reported Context (1)
- only eyebrow-raising advisory item, in fact, comes from the OpenSSL Software Foundation, warning of CVE-2026-34182 – an improper validation of an integrity-check value (CWE-354) concerning CMS (Cryptographic Message Microsoft’s September Patch Tuesday Addresses 973 CVEs Across 39 Product Families
CVE (41)
Vendors (4)
Products (36)
Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.
