Skip to content
Noroxi
NVD / CVE Program· CNA libreswan

CVE-2026-14957: FIPS mode assertion failure via malicious CERT payload

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: azl3 libreswan 4.15-2 on Azure Linux 3.0 4.15-3.

Low priority for now. Upgrade to azl3 libreswan 4.15-2 on Azure Linux 3.0 4.15-3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In FIPS mode, Libreswan's add_decoded_cert() function calls CERT_ExtractPublicKey() and asserts that the result is not NULL. However, CERT_ExtractPublicKey() returns NULL when public key extraction fails, for example if the RSA exponent is set to 0. A remote attacker can send a malformed X.509 certificate in a CERT payload to trigger the assertion, causing the pluto daemon to abort and restart. Continued exploitation causes a denial of service. No remote code execution is possible. Both IKEv1 and IKEv2 are affected. The vulnerability is only exploitable when both the OS and libreswan are running in FIPS mode and at least one CA certificate is loaded. The CERT payload is processed before peer authentication, so no credentials are needed to exploit this. Configurations using only PreSharedKey (PSK) authentication with no CA certificates loaded in the NSS database are not vulnerable.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Sep 1, 2026
Updated
Sep 9, 2026
EPSS
0.4% · 40th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · libreswan
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-14957

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (libreswan). Independent of NVD's CPE analysis and usually ahead of it.

  • The Libreswan Project libreswan

    • 5.3.2not affected
    • 3.0 and later · up to and including 5.3.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10libreswanbefore 5.3.2-1.el10_25.3.2-1.el10_2
AlmaLinux:10libreswan-minimalbefore 5.3.2-1.el10_25.3.2-1.el10_2
AlmaLinux:8libreswanbefore 4.12-2.el8_10.64.12-2.el8_10.6
AlmaLinux:9libreswanbefore 4.15-10.el9_84.15-10.el9_8
Alpine:v3.23libreswanbefore 5.3.3-r05.3.3-r0
Alpine:v3.24libreswanbefore 5.3.2-r05.3.2-r0
Debian:12libreswanfrom 0—
Debian:14libreswanbefore 5.2-2.55.2-2.5
Red Hat:enterprise_linux_eus:10.0libreswanbefore 0:5.2-1.el10_0.50:5.2-1.el10_0.5
Red Hat:enterprise_linux:10.2libreswanbefore 0:5.3.2-1.el10_20:5.3.2-1.el10_2
Red Hat:enterprise_linux:10.2libreswan-debugsourcebefore 0:5.3.2-1.el10_20:5.3.2-1.el10_2
Red Hat:enterprise_linux:10.2libreswan-minimalbefore 0:5.3.2-1.el10_20:5.3.2-1.el10_2
Red Hat:enterprise_linux:10.2libreswan-minimal-debuginfobefore 0:5.3.2-1.el10_20:5.3.2-1.el10_2
Red Hat:enterprise_linux:8::appstreamlibreswanbefore 0:4.12-2.el8_10.60:4.12-2.el8_10.6
Red Hat:enterprise_linux:8::appstreamlibreswan-debuginfobefore 0:4.12-2.el8_10.60:4.12-2.el8_10.6
Red Hat:enterprise_linux:8::appstreamlibreswan-debugsourcebefore 0:4.12-2.el8_10.60:4.12-2.el8_10.6
Red Hat:enterprise_linux:9::appstreamlibreswanbefore 0:4.15-10.el9_80:4.15-10.el9_8
Red Hat:enterprise_linux:9::appstreamlibreswan-debuginfobefore 0:4.15-10.el9_80:4.15-10.el9_8
Red Hat:enterprise_linux:9::appstreamlibreswan-debugsourcebefore 0:4.15-10.el9_80:4.15-10.el9_8
Red Hat:enterprise_linux:9::fastdatapathlibreswanbefore 0:5.3.2-1.el9fdp0:5.3.2-1.el9fdp
Red Hat:enterprise_linux:9::fastdatapathlibreswan-debuginfobefore 0:5.3.2-1.el9fdp0:5.3.2-1.el9fdp
Red Hat:enterprise_linux:9::fastdatapathlibreswan-debugsourcebefore 0:5.3.2-1.el9fdp0:5.3.2-1.el9fdp
Red Hat:rhel_aus:8.4::appstreamlibreswanbefore 0:4.3-6.el8_4.20:4.3-6.el8_4.2
Red Hat:rhel_aus:8.6::appstreamlibreswanbefore 0:4.5-1.el8_6.60:4.5-1.el8_6.6

+7

Other highest-scoring records for the same primary product.

  • CVE-2026-94453IKEv2 Use-After-Free bug when using IKE-over-TCP
    30Monitor
  • CVE-2026-77207Null Pointer Dereference in PKCS#7 bundle with no certificates
    30Monitor
  • CVE-2026-77206IKEv2 pre-authentication Null Pointer Dereference in EAP code
    30Monitor

Published before and after this one in the same product

  • Later →CVE-2026-77205Oct 13, 2026 · Denial of Service via sending bogus X.509 certificates
    14Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 libreswan 4.15-2 on Azure Linux 3.04.15-3Microsoft (MSRC)
almalinux:libreswan4.12-2.el8_10.6 · AlmaLinux:8Package registry (OSV)
almalinux:libreswan-minimal5.3.2-1.el10_2 · AlmaLinux:10Package registry (OSV)
alpine:libreswan5.3.3-r0 · Alpine:v3.23Package registry (OSV)
debian:libreswan5.2-2.5 · Debian:14Package registry (OSV)
red hat:libreswan0:4.12-2.el8_10.6 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:libreswan-debuginfo0:4.12-2.el8_10.6 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:libreswan-debugsource0:4.12-2.el8_10.6 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:libreswan-minimal0:5.3.2-1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:libreswan-minimal-debuginfo0:5.3.2-1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
rocky linux:libreswan0:4.12-2.el8_10.6 · Rocky Linux:8Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-7720742 days apartNull Pointer Dereference in PKCS#7 bundle with no certificates
    30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records