CVE-2026-42768: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt()

Published May 27, 2026
·
Updated

Issue summary: The CMSdecrypt and PKCS7decrypt 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.

Other sources

Multi-RecipientInfo Bleichenbacher Oracle in CMSdecrypt() and PKCS7decrypt()

Microsoft

Affected Software

7 affected componentsFixes available
OpenSSL OpenSSL
debian/openssl<=3.5.6-1~deb13u1, <=3.6.2-1
1.1.1w-0+deb11u11.1.1w-0+deb11u73.0.20-1~deb12u13.0.20-1~deb12u23.5.6-1~deb13u2
OpenSSL OpenSSL>=3.4.0<3.4.6
OpenSSL OpenSSL>=3.5.0<3.5.7
OpenSSL OpenSSL>=3.6.0<3.6.3
OpenSSL OpenSSL=4.0.0
Microsoft azl3 openssl 3.3.7-1<3.3.7-3
3.3.7-3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/openssl to a version that resolves this vulnerability.

    Fixed in 1.1.1w-0+deb11u1Fixed in 1.1.1w-0+deb11u7Fixed in 3.0.20-1~deb12u1Fixed in 3.0.20-1~deb12u2Fixed in 3.5.6-1~deb13u2
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.3.7-3
  3. Upgrade

    Upgrade OpenSSL to a version that resolves this vulnerability.

    Fixed in 3.4.5
  4. Upgrade

    Upgrade OpenSSL to a version that resolves this vulnerability.

    Fixed in 3.5.6
  5. Upgrade

    Upgrade OpenSSL to a version that resolves this vulnerability.

    Fixed in 3.6.2
  6. Upgrade

    Upgrade OpenSSL to a version that resolves this vulnerability.

    Fixed in 4.0.1
  7. Configuration

    When using CMS_decrypt() or PKCS7_decrypt() for RSA PKCS#1 v1.5 Key Transport, provide the recipient certificate to identify the specific RecipientInfo for decryption (avoid the case where the last RecipientInfo producing a key that looks valid will be used, or where a random key is substituted).

    OpenSSL CMS_decrypt()/PKCS7_decrypt() recipient certificate provided to select RecipientInfo = required
  8. Configuration

    Ensure EVP_PKEY_decrypt() uses the implicit rejection mechanism described in draft-irtf-cfrg-rsa-guidance when RSA PKCS#1 v1.5 Key Transport is in use (previous OpenSSL releases explicitly disabled implicit rejection; this change mitigates the Bleichenbacher oracle branches).

    OpenSSL EVP_PKEY_decrypt() RSA PKCS#1 v1.5 implicit rejection mechanism = implicit rejection mechanism enabled

Event History

May 27, 2026
Data Sourced
via Red Hat·02:19 PM
DescriptionSeverityAffected Software
Jun 9, 2026
CVE Published
via MITRE·04:03 PM
Data Sourced
via MITRE·04:03 PM
DescriptionWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
RemedyAffected Software
Data Sourced
via Ubuntu·08:07 PM
RemedyDescriptionSeverityAffected Software
Jun 10, 2026
Data Sourced
via Debian·08:09 PM
DescriptionAffected Software
Data Sourced
via Launchpad·08:09 PM
Description
Jun 13, 2026
Data Sourced
via Microsoft·08:03 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:03 AM
Affected Software
Updated
via Microsoft·08:03 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-42768?

The severity of CVE-2026-42768 is rated low with a CVSS score of 3.7.

2

How do I fix CVE-2026-42768?

To fix CVE-2026-42768, update to the latest version of OpenSSL where the vulnerability has been addressed.

3

What types of attacks are associated with CVE-2026-42768?

CVE-2026-42768 is associated with Bleichenbacher-style attacks targeting the CMS_decrypt and PKCS7_decrypt functions.

4

What software is affected by CVE-2026-42768?

CVE-2026-42768 affects OpenSSL and specifically the CMS_decrypt and PKCS7_decrypt functions.

5

Can CVE-2026-42768 lead to data compromise?

Yes, CVE-2026-42768 can potentially lead to data compromise if attackers can exploit the decryption functions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203