CVE
Libreswan denial of service in X509 PKCS#7 handling
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 5.4.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.4.2.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Libreswan pluto daemon in libreswan crashes and restarts when it receives a CERT payload with an empty PKCS#7 payload. An attacker can trigger this remotely, without logging in, which can lead to denial of service; remote code execution is not possible.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
The Libreswan pluto daemon dereferences a NULL pointer when a CERT payload is received with an empty PKCS#7 payload, causing the daemon to crash and restart. The NSS function SEC_PKCS7GetCertificateList() was used to check whether the content was empty, but this check did not trigger if the non-empty content of the PKCS#7 wrapped payload was an empty list. Continued triggering of this vulnerability can lead to a denial of service. Remote code execution is not possible. Authentication is not required to trigger this vulnerability.
Who should check
Teams running Libreswan IKE/IPsec VPN gateways (pluto daemon) in versions 3.24 through 5.4.1.
Not fixed by: There is no workaround; apply the patch or upgrade to 5.4.2 or later.
“Vulnerable versions : 3.24 up to and including 5.4.1”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.4.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-110339 (x509 NULL pointer dereference on empty PKCS#7 payload), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-110339 (entry last updated 2026-11-16):
Affected:
- The Libreswan Project libreswan: from 3.24, through 5.4.1
Fixed versions: 5.4.2.
Conditions (all must be true for the bug to be hit):
- Libreswan versions 3.24 up to and including 5.4.1 are affected. (source: https://libreswan.org/security/CVE-2026-110339/CVE-2026-110339.txt)
- A CERT payload must be received with an empty PKCS#7 payload. (source: https://libreswan.org/security/CVE-2026-110339/CVE-2026-110339.txt)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-110339 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110339 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://libreswan.org/security/CVE-2026-110339/CVE-2026-110339.txt
- https://libreswan.org/security/CVE-2026-110339/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-110339
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110339"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- libreswan
From 3.24 · through 5.4.1
Evidence 4
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Advisory
- Patch
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-110339
Is CVE-2026-110339 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted CERT payload carrying an empty PKCS#7 payload can make the IKE daemon pluto dereference a NULL pointer while processing x509 data. Repeated triggering can crash and restart pluto, causing a denial of service.Source: libreswan.org
Which versions are affected by CVE-2026-110339?
libreswan: from 3.24 through 5.4.1.Source: cve.now feed data
Am I affected, and how do I check?
Libreswan versions 3.24 up to and including 5.4.1 are affected, and only when a CERT payload is received with an empty PKCS#7 payload. To check a system, run ipsec version to see the installed Libreswan version.Source: libreswan.org
How do I fix CVE-2026-110339?
Upgrade to libreswan 5.4.2 or later, which the advisory names as the fix.Source: libreswan.org