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-42768

openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt()

Overview

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

Description

Issue summary: The CMS_decrypt and PKCS7_decrypt functions are vulnerable to Bleichenbacher-style attack when an attacker is able to provide the CMS or S/MIME messages and observe the error code and/or decryption output.

Impact summary: The Bleichenbacher-style attack allows an attacker to use the victim's vulnerable application as a way to decrypt or sign messages with the victim's private RSA key.

The attack is possible in 2 variants.

  1. The decryption API (CMS_decrypt(), PKCS7_decrypt()) is used without providing the recipient certificate. In this case OpenSSL iterates over every KeyTransRecipientInfo (KTRI) without stopping at the first success.

An attacker who authors a message with two KTRI entries — the first one wrapping a real CEK under the victim's public key, the second with an arbitrary probe ciphertext — obtains opportunity to iterate the 2nd KTRI to get a valid PKCS#1 v1.5 padding if the error code of the application is available.

That is a Bleichenbacher oracle (Bleichenbacher, CRYPTO '98): an adaptive-chosen-ciphertext side channel from which the attacker decrypts any RSA ciphertext to the victim's key or forges any PKCS#1 v1.5 signature under it.

  1. When the decryption API (CMS_decrypt(), PKCS7_decrypt()) is provided with the recipient certificate, and the recipient is not found, a random key is substituted.

An attacker who authors a message and is able to compare both error code and the result of the decryption, can mount a Bleichenbacher oracle.

We are not aware of any applications that provide a remote attacker an opportunity to mount an attack described in these scenarios. We consider the existence of such application very unlikely, and for this reason this CVE has been evaluated as Low severity.

To avoid these attacks, when RSA PKCS#1 v1.5 Key Transport is in use, the invoked EVP_PKEY_decrypt() will use the implicit rejection mechanism described in draft-irtf-cfrg-rsa-guidance. In previous OpenSSL releases the implicit rejection was explicitly disabled.

The implicit rejection mechanism always returns a plaintext value, the symmetric key. This result is deterministic for the ciphertext and the private key. The length of the decryption result can happen to match the length of the key of the symmetric cipher that was used for the content encryption. When a certificate is not provided, the last RecipientInfo producing a key that looks valid will be used. It may cause getting garbage content on decryption. As a proper way to deal with this a recipient certificate has to be provided to identify the particular RecipientInfo for decryption.

The FIPS modules in 4.0, 3.6, 3.5, and 3.4 are not affected by this issue, as CMS and S/MIME processing happens outside the OpenSSL FIPS module boundary.

Source: OX vulnerability database

Severity

3.7 · LOW

CVSS 3.1 base score, scored by NVD.

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

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

Weakness: CWE-514

Affected packages · 3

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

Open a package to see all its vulnerabilities.

Operating systems · 42 fixes

Azure Linux 1 release · 1 package

fixed 1
openssl
Azure Linux fixes for CVE-2026-42768
ReleasePackageFixed in
3.0 openssl 0:3.3.7-3.azl3

Oracle Linux 1 release · 1 package

fixed 2
openssl
Oracle Linux fixes for CVE-2026-42768
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 1 release · 1 package

fixed 1
openssl
Photon OS fixes for CVE-2026-42768
ReleasePackageFixed in
5.0 openssl +5 3.5.7-1.ph5

Red Hat 3 releases · 4 packages

affected 3 fixed 1
aavmf compat-openssl10 compat-openssl11 openssl
Red Hat fixes for CVE-2026-42768
ReleasePackageFixed inAdvisory
7 aavmf +3 affected —
8 compat-openssl10 +18 affected —
9 compat-openssl11 +12 affected —
9 openssl +3 1:3.5.5-4.el9_8 RHSA-2026:25239

SUSE Linux Enterprise 2 releases · 1 package

fixed 2
libopenssl-3-devel
SUSE Linux Enterprise fixes for CVE-2026-42768
ReleasePackageFixed inAdvisory
15.7 libopenssl-3-devel +5 3.2.3-150700.5.36.1 SUSE-SU-2026:2648-1
16.0 libopenssl-3-devel +6 3.5.0-160000.8.1 SUSE-SU-2026:22315-1

SUSE Linux Enterprise Micro 1 release · 1 package

fixed 1
libopenssl-3-devel
SUSE Linux Enterprise Micro fixes for CVE-2026-42768
ReleasePackageFixed inAdvisory
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-42768
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-42768
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-42768
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-42768
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 2 releases · 1 package

fixed 2
openssl
debian fixes for CVE-2026-42768
ReleasePackageFixed in
13 openssl 3.5.6-1~deb13u2
14 openssl 3.6.3-1

echo 1 release · 2 packages

fixed 2
openssl-3-5-0 openssl
echo fixes for CVE-2026-42768
ReleasePackageFixed in
openssl-3-5-0 3.5.0+e1
openssl 3.5.6-1~deb13u2

minimos 1 release · 1 package

fixed 1
openssl
minimos fixes for CVE-2026-42768
ReleasePackageFixed in
openssl 3.5.7-r0

openSUSE 1 release · 1 package

fixed 1
libopenssl-3-devel
openSUSE fixes for CVE-2026-42768
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-42768
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-42768
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 5
openssl
seal Red Hat fixes for CVE-2026-42768
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-14.el8_6+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 2
openssl seal-openssl
seal alpine fixes for CVE-2026-42768
ReleasePackageFixed in
openssl 3.3.3-r0000
seal-openssl 3.3.3-r053413

seal debian 1 release · 1 package

fixed 1
openssl
seal debian fixes for CVE-2026-42768
ReleasePackageFixed in
openssl +1 3.5.4-1~deb13u1+sp999

ubuntu 2 releases · 2 packages

affected 1 fixed 1
nodejs openssl
ubuntu fixes for CVE-2026-42768
ReleasePackageFixed in
22.04 nodejs affected
26.04 openssl 3.5.5-1ubuntu3.2

wolfi 1 release · 2 packages

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

References

Show all 66 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.