Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-34182

openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages

Overview

Published
9 Jun 2026
Modified
23 Jul 2026
Critical CVE
3 Registry packages
39 OS packages
21 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

9.1 · CRITICAL

CVSS 3.1 base score, scored by NVD.

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

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

Weakness: CWE-354

Affected packages · 3

Packages affected by CVE-2026-34182
EcosystemPackageVulnerableFixed in
Julia AppBundler >=1.0.0, <1.0.1 1.0.1
Julia Openresty_jll >=1.27.1+0 No fix yet
Julia OpenSSL_jll >=3.0.8+0, <3.5.7+0 3.5.7+0

Open a package to see all its vulnerabilities.

Operating systems · 66 fixes

Azure Linux 1 release · 2 packages

fixed 2
edk2 openssl
Azure Linux fixes for CVE-2026-34182
ReleasePackageFixed in
3.0 edk2 0:20240524git3e722403cd16-18.azl3
3.0 openssl 0:3.3.7-2.azl3

Oracle Linux 1 release · 1 package

fixed 2
openssl
Oracle Linux fixes for CVE-2026-34182
ReleasePackageFixed in
9 openssl +3 10:3.5.5-4.0.1.el9_8_fips
9 openssl +3 1:3.5.5-4.0.1.el9_8

Photon OS 2 releases · 1 package

fixed 2
openssl
Photon OS fixes for CVE-2026-34182
ReleasePackageFixed in
4.0 openssl +4 3.0.21-1.ph4
5.0 openssl +5 3.5.7-1.ph5

Red Hat 3 releases · 2 packages

affected 3 fixed 4
openshift-ose-rhel-coreos-9 openssl
Red Hat fixes for CVE-2026-34182
ReleasePackageFixed inAdvisory
7 openshift-ose-rhel-coreos-9 affected —
8 openshift-ose-rhel-coreos-9 affected —
9 openshift-ose-rhel-coreos-9 affected —
9 openssl +1 1:3.0.7-18.el9_2.4 RHSA-2026:84572
9 openssl +1 1:3.0.7-29.el9_4.3 RHSA-2026:84573
9 openssl +3 1:3.2.2-7.el9_6.4 RHSA-2026:83617

1 more row

SUSE Linux Enterprise 5 releases · 3 packages

fixed 7
libopenssl-3-devel nodejs24 libopenssl-devel
SUSE Linux Enterprise fixes for CVE-2026-34182
ReleasePackageFixed inAdvisory
15.4 libopenssl-3-devel +2 3.0.8-150400.4.90.1 SUSE-SU-2026:3094-1
15.5 libopenssl-3-devel +2 3.0.8-150500.5.69.1 SUSE-SU-2026:3005-1
15.6 libopenssl-3-devel +5 3.1.4-150600.5.53.1 SUSE-SU-2026:2393-1
15.7 nodejs24 +3 24.18.1-150700.15.18.1 SUSE-SU-2026:3835-1
15.7 libopenssl-devel +2 3.5.0-150700.3.4.1 SUSE-SU-2026:3835-1
15.7 libopenssl-3-devel +5 3.5.0-150700.5.45.2 SUSE-SU-2026:3835-1

1 more row

SUSE Linux Enterprise Micro 5 releases · 2 packages

fixed 5
libopenssl3 libopenssl-3-devel
SUSE Linux Enterprise Micro fixes for CVE-2026-34182
ReleasePackageFixed inAdvisory
5.3 libopenssl3 3.0.8-150400.4.90.1 SUSE-SU-2026:3094-1
5.4 libopenssl3 3.0.8-150400.4.90.1 SUSE-SU-2026:3094-1
6.0 libopenssl-3-devel +3 3.1.4-14.1 SUSE-SU-2026:22100-1
6.1 libopenssl-3-devel +3 3.1.4-slfo.1.1_10.1 SUSE-SU-2026:22132-1
6.2 libopenssl-3-devel +3 3.5.0-160000.8.1 SUSE-SU-2026:22251-1

alma 1 release · 1 package

fixed 1
openssl
alma fixes for CVE-2026-34182
ReleasePackageFixed in
9 openssl +3 1:3.5.5-4.el9_8

alpine 4 releases · 1 package

fixed 4
openssl
alpine fixes for CVE-2026-34182
ReleasePackageFixed in
3.22 openssl 3.5.7-r0
3.23 openssl 3.5.7-r0
3.24 openssl 3.5.7-r0
edge openssl 3.5.7-r0

amazon linux 1 release · 1 package

fixed 1
openssl
amazon linux fixes for CVE-2026-34182
ReleasePackageFixed in
2023 openssl +10 1:3.5.5-1.amzn2023.0.5

chainguard 1 release · 4 packages

not affected 1 fixed 3
openssl-provider-fips-3-4-0 openssl-3-5 libcrypto3-2-34 openssl-4-0
chainguard fixes for CVE-2026-34182
ReleasePackageFixed in
openssl-provider-fips-3-4-0 +1 not affected
openssl-3-5 3.5.7-r0
libcrypto3-2-34 +1 3.6.3-r0
openssl-4-0 4.0.1-r0

debian 3 releases · 1 package

fixed 3
openssl
debian fixes for CVE-2026-34182
ReleasePackageFixed in
12 openssl 3.0.20-1~deb12u2
13 openssl 3.5.6-1~deb13u2
14 openssl 3.6.3-1

echo 1 release · 4 packages

fixed 4
openssl openssl-3-0-9 openssl-3-1-0 openssl-3-5-0
echo fixes for CVE-2026-34182
ReleasePackageFixed in
openssl 3.0.20-1~deb12u2
openssl-3-0-9 3.0.9+e1
openssl-3-1-0 3.1.0+e1
openssl-3-5-0 3.5.0+e1

minimos 1 release · 2 packages

fixed 2
openssl-3-0 openssl
minimos fixes for CVE-2026-34182
ReleasePackageFixed in
openssl-3-0 3.0.21-r0
openssl 3.5.7-r0

openSUSE 1 release · 1 package

fixed 1
libopenssl-3-devel
openSUSE fixes for CVE-2026-34182
ReleasePackageFixed inAdvisory
Tumbleweed libopenssl-3-devel +9 3.5.3-6.1 openSUSE-SU-2026:11023-1

openSUSE Leap 1 release · 1 package

fixed 1
libopenssl-3-devel
openSUSE Leap fixes for CVE-2026-34182
ReleasePackageFixed inAdvisory
16.0 libopenssl-3-devel +6 3.5.0-160000.8.1 openSUSE-SU-2026:21005-1

rocky 2 releases · 1 package

fixed 2
openssl
rocky fixes for CVE-2026-34182
ReleasePackageFixed in
10 openssl +1 1:3.5.5-4.el10_2
9 openssl +1 1:3.5.5-4.el9_8

seal Red Hat 3 releases · 1 package

fixed 4
openssl
seal Red Hat fixes for CVE-2026-34182
ReleasePackageFixed in
7 openssl +1 1:1.0.2k-25.el7_9+sp999
7 openssl +1 1:1.0.2k-26.el7_9+sp999
8 openssl +1 1:1.1.1k-6.el8_5+sp999
9 openssl +1 1:3.2.2-6.el9_5+sp999

seal alpine 1 release · 2 packages

fixed 3
openssl seal-openssl
seal alpine fixes for CVE-2026-34182
ReleasePackageFixed in
openssl +1 3.3.2-r45341999
openssl 3.3.3-r0000
seal-openssl 3.3.3-r053413

seal debian 1 release · 1 package

fixed 6
openssl
seal debian fixes for CVE-2026-34182
ReleasePackageFixed in
openssl +1 3.0.11-1~deb12u2+sp999
openssl +1 3.0.13-0ubuntu3.4+sp999
openssl +1 3.0.16-1~deb12u1+sp999
openssl +1 3.0.2-0ubuntu1.19+sp999
openssl +1 3.0.2-0ubuntu1.20+sp999
openssl +1 3.5.4-1~deb13u1+sp999

ubuntu 3 releases · 1 package

fixed 3
openssl
ubuntu fixes for CVE-2026-34182
ReleasePackageFixed in
22.04 openssl 3.0.2-0ubuntu1.25
24.04 openssl 3.0.13-0ubuntu3.11
26.04 openssl 3.5.5-1ubuntu3.2

wolfi 1 release · 2 packages

fixed 2
openssl openssl-4-0
wolfi fixes for CVE-2026-34182
ReleasePackageFixed in
openssl 3.6.3-r0
openssl-4-0 4.0.1-r0

References

Show all 69 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.