
An installed VPN package is an inventory lead. A running, reachable IKE service is the exposure check that makes this Libreswan update operationally relevant.
What changed — November 19, 2026 UTC
CVE-2026-110339: Microsoft’s November CVRF record, revision 3.0 dated November 19 at 01:04:30 UTC, now maps an Azure Linux 4.0 affected package and fixed build. Microsoft’s first revision is dated November 17 at 19:36:27 UTC. This finding was previously held for package and applicability verification; the mapping and repository availability are now verified. The Libreswan Project published its underlying advisory and version 5.4.2 on November 16.
Libreswan says an unauthenticated attacker can send a CERT payload containing an empty PKCS#7 certificate list to crash and restart the pluto IKE daemon. Repeated triggering can sustain denial of service. The vendor explicitly rules out remote code execution for this flaw. Check whether Libreswan/pluto is actually running and reachable by an untrusted sender; package presence alone does not establish that exposure.
Microsoft rates the mapped issue Important, CVSS v3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Libreswan assigns a Medium vendor severity because the daemon restarts and sustained denial of service requires repeated triggering. Its CNA record publishes the same CVSS v3.1 score of 7.5.
Affected versions and available fixes
| Product or package | Affected applicability | Verified fix |
|---|---|---|
| Upstream Libreswan | 3.24 through 5.4.1 inclusive | 5.4.2 or later; official patches also available |
| Azure Linux 4.0 Libreswan | MSRC lists exact build 5.4.1-4.azl4 | 0:5.4.2-2.azl4 |
| Azure Linux 3.0 Libreswan — existing context | MSRC lists exact build 4.15-4 | No fixed build populated in the reviewed MSRC row |
The Azure Linux rows are exact listed package builds, not verified lower bounds for every distribution build or backport. Libreswan identifies upstream 3.0–3.23 and 5.4.2 or later as not vulnerable. For Azure Linux 4.0, checksum-verified official Microsoft repository metadata lists 5.4.2-2.azl4 for x86_64 and aarch64, and both exact RPM URLs loaded successfully. Those binaries were already hosted on November 17: this is newly verified remediation mapping, not a claim that new binaries appeared today. Availability does not prove customer installation or inclusion in any particular Azure or AKS image.
Suggested MSP priority and action
Suggested priority: High for an affected, reachable customer VPN/IKE service. Inventory the OS branch, installed package, running pluto build and actual exposure → restrict unnecessary IKE reachability to required peers where the design permits, recognizing that this is proposed exposure reduction and not a vendor workaround → stage a supported distribution update, using the verified Azure Linux 4.0 build above; obtain a supported fix determination for the Azure Linux 3.0 row → verify the running daemon uses the updated package and test tunnel establishment, rekeying and representative traffic. Plan service interruption and redundancy with the environment owner; do not assume a package update has restarted the daemon.
Libreswan states there is no workaround and directs customers to patch or upgrade. Do not manually substitute an upstream build inside a vendor-managed appliance or managed node image. No reviewed source establishes that a Fortinet, Cisco or other covered appliance uses the vulnerable component; investigate bundled dependencies separately.
The full current CISA KEV catalog does not list CVE-2026-110339, so there is no associated federal KEV deadline. Confirmed active exploitation was not verified in the reviewed official material. No vendor-directed compromise-check or blanket credential-rotation requirement was identified. No Brian or customer deployment or compromise is assumed.
Official evidence and limits
MSRC CVE advisory · MSRC November CVRF data · Libreswan advisory and remediation · Libreswan-authored CNA record · Microsoft x86_64 repository metadata · Microsoft aarch64 repository metadata · Microsoft Azure Linux update guidance · CISA official KEV data
Last verified November 19, 2026 ET. Microsoft’s API and repository data were accessible even though its individual web advisory was unavailable through one retrieval route. Other Azure Linux dependency changes remain under review, and existing vendor-source access gaps remain open.