CVE-2026-34182

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.

Read the notes from the security team

Status

Show unmaintained releases

Package	Ubuntu Release	Status
edk2	26.04 LTS resolute	Needs evaluation
	25.10 questing	Needs evaluation
	24.04 LTS noble	Needs evaluation
	22.04 LTS jammy	Not affected
	20.04 LTS focal	Not affected
	18.04 LTS bionic	Not affected
nodejs	26.04 LTS resolute	Not affected
	25.10 questing	Not affected
	24.04 LTS noble	Not affected
	22.04 LTS jammy	Vulnerable
	20.04 LTS focal	Not affected
	18.04 LTS bionic	Not affected
	14.04 LTS trusty	Not affected
openssl	26.04 LTS resolute	Fixed 3.5.5-1ubuntu3.2
	25.10 questing	Fixed 3.5.3-1ubuntu3.4
	24.04 LTS noble	Fixed 3.0.13-0ubuntu3.11
	22.04 LTS jammy	Fixed 3.0.2-0ubuntu1.25
	20.04 LTS focal	Not affected
	18.04 LTS bionic	Not affected
	16.04 LTS xenial	Not affected
	14.04 LTS trusty	Not affected
openssl-fips	26.04 LTS resolute	Not in release
	25.10 questing	Not in release
	24.04 LTS noble	Not in release
	22.04 LTS jammy	Not in release
openssl1.0	26.04 LTS resolute	Not in release
	25.10 questing	Not in release
	24.04 LTS noble	Not in release
	22.04 LTS jammy	Not in release
	18.04 LTS bionic	Not affected

Notes

mdeslaur

edk2 in jammy embeds OpenSSL 1.1.1j edk2 in noble embeds OpenSSL 3.0.9 edk2 in plucky embeds OpenSSL 3.4.0 edk2 in questing embeds OpenSSL 3.4.0 nodejs in jammy embeds OpenSSL 1.1.1m OpenSSL 4.0, 3.6, 3.5, 3.4, and 3.0 are vulnerable to this issue.

Severity score breakdown

CVSS version: CVSS v3.0

Base score 9.1 · Critical

Base metrics

Parameter	Value
Attack vector	Network
Attack complexity	Low
Privileges required	None
User interaction	None
Scope	Unchanged
Confidentiality impact	High
Integrity impact	High
Availability impact	None

Scores

Parameter	Value
Base score	9.1 · Critical
Exploitability score	-
Impact score	-

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

References

Related Ubuntu Security Notices (USN)

USN-8414-2
OpenSSL vulnerabilities
9 June 2026

USN-8414-1
OpenSSL vulnerabilities
9 June 2026