High [CVE-2026-50721] IKEv1 Denial of Service via RSA-SHA1 (PKCS#1 Version 1.5 Encrypted) authentication payload
This high-severity Red Hat Linux advisory covers CVE-2026-50721 affecting Fast Datapath for Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published
Summary
Libreswan, via the function RSA_authenticate_hash_signature_raw_rsa(), 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. A remote, unauthenticated attacker could exploit this vulnerability by sending a specially crafted IKEv1 packet containing a shorter-than-expected hash payload.
This triggers an assertion failure within the Libreswan daemon, causing it to crash and restart, leading to a persistent Denial of Service (DoS) condition if malicious packets are continuously transmitted.
Additionally, if the target system relies on RSA keys with weak public exponents (e.g., e=3), a Bleichenbacher-style signature forgery attack may be feasible, potentially allowing the attacker to bypass authentication entirely.
Is CVE-2026-50721 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-50721 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-50721?
Upgrade to a fixed release named by Red Hat:
- libreswan-0:5.3.2-1.el9fdp
- libreswan-0:5.3.2-1.el10_2
- libreswan-0:5.2-1.el10_0.5
- libreswan-0:4.12-2.el8_10.6
- libreswan-0:4.3-6.el8_4.2
- libreswan-0:4.5-1.el8_6.6
- libreswan-0:4.9-3.el8_8.3
- libreswan-0:4.15-10.el9_8
- libreswan-0:4.9-5.el9_2.5
- libreswan-0:4.12-3.el9_4.2
- libreswan-0:4.15-8.el9_6.1
- openshift/ose-rhel-coreos-9:4.19.9.6.202609021231-0
16 more fixed releases are listed below.
Confirm against the vendor advisory before you patch.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
- libreswan-0:5.3.2-1.el9fdp
- libreswan-0:5.3.2-1.el10_2
- libreswan-0:5.2-1.el10_0.5
- libreswan-0:4.12-2.el8_10.6
- libreswan-0:4.3-6.el8_4.2
- libreswan-0:4.5-1.el8_6.6
- libreswan-0:4.9-3.el8_8.3
- libreswan-0:4.15-10.el9_8
- libreswan-0:4.9-5.el9_2.5
- libreswan-0:4.12-3.el9_4.2
- libreswan-0:4.15-8.el9_6.1
- openshift/ose-rhel-coreos-9:4.19.9.6.202609021231-0
- openshift/ose-rhel-coreos-9:4.20.9.6.202609021029-0
- openshift/ose-rhel-coreos-9:4.21.9.6.202609021100-0
- RHSA-2026:46986
- RHSA-2026:46398
- RHSA-2026:55449
- RHSA-2026:46396
- RHSA-2026:84887
- RHSA-2026:82154
- RHSA-2026:72287
- RHSA-2026:46397
- RHSA-2026:61779
- RHSA-2026:61258
- RHSA-2026:57741
- RHSA-2026:63044
- RHSA-2026:63100
- RHSA-2026:63041
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Mitigation checklist
- To mitigate this vulnerability, consider the following strategic workarounds if upgrading Libreswan immediately is not viable: - Migrate to IKEv2: Disable IKEv1 entirely and migrate all connections to IKEv2. The vulnerable code path is tied specifically to IKEv1’s rigid handling of PKCS#1 v1.5 RSA-SHA1. - Switch to Pre-Shared Keys (PSK): Additionally, if the configuration is for static tunnels, and not for a group of Remote Access VPN Clients, the authentication can be changed to use PSK via "authby=secret" after coordination with the remote peer.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Get an email when Red Hat RHEL & SELinux publishes the next one.
See Red Hat RHEL & SELinux's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
More Red Hat Linux advisories
- CVE-2026-46300May 13, 2026"Fragnesia" is a variant of Dirty Frag vulnerability in the ESP/XFRM leading to Local
- CVE-2026-31431Apr 22, 2026algif_aead - Revert to operating out-of-place
- CVE-2026-34486Apr 9, 2026Missing Encryption of Sensitive Data due to EncryptInterceptor bypass
- CVE-2025-31277Mar 18, 2026Processing maliciously crafted web content may lead to memory corruption
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-53362Jul 4, 2026account for fraggap on the paged allocation path
iPhone and Android apps · New on the App Store
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.