CVE-2026-50721: IKEv1 Denial of Service via RSA-SHA1 (PKCS#1 Version 1.5 Encrypted) authentication payload

Published Jun 29, 2026
·
Updated

IKEv1 Denial of Service via RSA-SHA1 (PKCS#1 Version 1.5 Encrypted) authentication payload

Other sources

Libreswan, via the function RSAauthenticatehashsignaturerawrsa(), did not correctly verify the length of the authentication hash when the SIG payload of an IKEv1 packet was encoded using PKCS #1 RSA Encryption as per RFC 2313. A remote attacker can use a variation on the Bleichenbacher attack to forge the SIG payload when small public exponents are being used (e.g., e=3), which could lead to impersonation. Additionally, a remote attacker, by encoding a shorter than expected hash in the SIG payload, could trigger an assertion leading to denial-of-service. The daemon aborts and restarts; continued exploitation causes sustained denial of service. Remote code execution is not possible. X.509 certificate verifications of remote IKE peers are not affected.

MITRE

The Libreswan Project was notified of an issue when it receives an invalidly formatted PKCS#1.5 RSA signature payload that authenticates the IKE exchange. The vulnerability is similar to CVE-2018-16151. Use of RSA signatures over certificates during X.509 certificate verifications of the remote IKE peer are not affected by this vulnerability.

When the RSA exponent is weak (eg e=3), Bleichenbacher-style signature forgeries are possible, resulting in an authentication bypass. Note that most cryptographic library versions and libreswan raw RSA key generation have not allowed weak exponents for at least a decade, so valid RSA keys with weak exponents should be very rare.

Additionally, the invalid RSA IKE authentication payload can trigger an assertion, resulting in libreswan aborting and restarting. Continued sending of such packets can result in a denial of service.

Severity : Medium Vulnerable versions : all version up to and including 5.3 Not vulnerable : 5.3.1 or later

Red Hat

Affected Software

3 affected componentsFixes available
libreswan Libreswan
libreswan Libreswan<5.3.1
Microsoft azl3 libreswan 4.15-1<4.15-2
4.15-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 4.15-2
  2. Upgrade

    Upgrade libreswan to a version that resolves this vulnerability.

    Fixed in 5.3.1

Event History

Jun 29, 2026
Data Sourced
via Red Hat·11:30 AM
DescriptionSeverityAffected Software
Jul 2, 2026
CVE Published
via MITRE·09:44 PM
Data Sourced
via MITRE·09:44 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeaknessAffected Software
Jul 4, 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-50721?

The severity of CVE-2026-50721 is high, rated at 8.1.

2

How do I fix CVE-2026-50721?

To fix CVE-2026-50721, update to the latest version of Libreswan that addresses this vulnerability.

3

What type of attack is associated with CVE-2026-50721?

CVE-2026-50721 is linked to a denial of service attack that can be executed via a flaw in RSA-SHA1 authentication payload.

4

What software is affected by CVE-2026-50721?

Libreswan is the software affected by CVE-2026-50721.

5

Can CVE-2026-50721 lead to data loss?

CVE-2026-50721 has a potential impact on availability, but it does not directly lead to data loss.

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