Bug 2501764 (CVE-2026-14957)
| Summary: | CVE-2026-14957 libreswan: badly formatted X.509 certificate can cause an assertion failure that crashes the daemon process | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security <prodsec-ir-bot> |
| Status: | NEW --- | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | akhatavk, aos-team-art-private, asdas, dpaolell, echaudro, fleitner, jdelft, jupierce, ktraynor, lgarciaa, mbiarnes, paul.wouters, ppalepu, ppostler, prdhamdh, rhel-process-autobot, rkhan, sghai, sidsharm, suppawar, vlaad, watson-tool-maintainers |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: |
A flaw was found in Libreswan. An unauthenticated remote attacker can send a specially crafted X.509 certificate payload during an IKEv1 or IKEv2 exchange. This flaw occurs when Libreswan is operating in FIPS (Federal Information Processing Standards) mode and processing a certificate with an invalid public key, such as an RSA exponent of zero. This can trigger an assertion failure, leading to the termination of the daemon process and a denial of service.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2501766 | ||
| Bug Blocks: | |||
|
Description
OSIDB Bzimport
2026-07-17 15:07:27 UTC
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:46396 https://access.redhat.com/errata/RHSA-2026:46396 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:46397 https://access.redhat.com/errata/RHSA-2026:46397 This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:46398 https://access.redhat.com/errata/RHSA-2026:46398 This issue has been addressed in the following products: Fast Datapath for Red Hat Enterprise Linux 9 Via RHSA-2026:46986 https://access.redhat.com/errata/RHSA-2026:46986 This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2026:55449 https://access.redhat.com/errata/RHSA-2026:55449 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:57741 https://access.redhat.com/errata/RHSA-2026:57741 this bug should be closed This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions Via RHSA-2026:61258 https://access.redhat.com/errata/RHSA-2026:61258 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2026:61779 https://access.redhat.com/errata/RHSA-2026:61779 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.20 Via RHSA-2026:63100 https://access.redhat.com/errata/RHSA-2026:63100 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.21 Via RHSA-2026:63041 https://access.redhat.com/errata/RHSA-2026:63041 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.19 Via RHSA-2026:63044 https://access.redhat.com/errata/RHSA-2026:63044 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions Red Hat Enterprise Linux 8.8 Telecommunications Update Service Via RHSA-2026:72287 https://access.redhat.com/errata/RHSA-2026:72287 |