CVE-2026-77205 (GCVE-0-2026-77205)
Vulnerability from cvelistv5 – Published: 2026-10-13 21:28 – Updated: 2026-10-16 15:31- CWE-772 - Missing Release of Resource after Effective Lifetime
| URL | Tags |
|---|---|
| https://libreswan.org/security/CVE-2026-77205/CVE… | vendor-advisory |
| https://libreswan.org/security/CVE-2026-77205/ | patch |
| https://libreswan.org/security/CVE-2026-14957/CVE… | related |
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| The Libreswan Project | libreswan |
Affected:
5.3 , ≤ 5.3.2
(semver)
Unaffected: 5.3.3 (semver) |
guessed |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-77205",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-16T15:14:28.040688Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-16T15:31:54.457Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://github.com/libreswan/libreswan",
"defaultStatus": "unaffected",
"packageName": "libreswan",
"product": "libreswan",
"programRoutines": [
{
"name": "add_decoded_cert"
}
],
"repo": "https://github.com/libreswan/libreswan",
"vendor": "The Libreswan Project",
"versions": [
{
"lessThanOrEqual": "5.3.2",
"status": "affected",
"version": "5.3",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "5.3.3",
"versionType": "semver"
}
]
}
],
"configurations": [
{
"lang": "en",
"value": "Only configurations running in FIPS mode are vulnerable. Verify FIPS mode and loaded CA certificates with \u0027sudo ipsec fipsstatus\u0027 and \u0027sudo ipsec listcacerts\u0027."
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Wojciech Tatarski (TuxCare)"
}
],
"descriptions": [
{
"lang": "en",
"value": "Libreswan in FIPS mode has a vulnerability where badly formed received certificates are rejected, but not deleted from the NSS cache. As a result, any real certificates with the same serial number are rejected as well. This can be abused to lock out legitimate peers from connecting. The add_decoded_cert() function missed a call to CERT_DestroyCertificate() due to an incorrect fix for CVE-2026-14957. Sending bogus certificates with new serial numbers could prevent the real certificates with those serial numbers from connecting until the service has restarted."
}
],
"exploits": [
{
"lang": "en",
"value": "No known exploitation in the wild. An attacker could trick a peer into connecting to them first to learn the serial number, then use that to prevent the peer from connecting to the legitimate server. Exploitation requires FIPS mode to be enabled."
}
],
"impacts": [
{
"descriptions": [
{
"lang": "en",
"value": "Denial of service by preventing legitimate peers from connecting through cache poisoning with bogus certificates"
}
]
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 3.7,
"baseSeverity": "LOW",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"other": {
"content": {
"description": "Vendor-assessed severity: Low. Exploitation requires FIPS mode to be enabled and either guessing or learning certificate serial numbers. Certificate Authorities should use randomized serial numbers per best practice.",
"value": "LOW"
},
"type": "vendorSeverity"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-772",
"description": "CWE-772: Missing Release of Resource after Effective Lifetime",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-13T21:28:03.390Z",
"orgId": "d42dc95b-23f1-4e06-9076-20753a0fb0df",
"shortName": "libreswan"
},
"references": [
{
"name": "Libreswan Security Advisory CVE-2026-77205",
"tags": [
"vendor-advisory"
],
"url": "https://libreswan.org/security/CVE-2026-77205/CVE-2026-77205.txt"
},
{
"name": "Libreswan CVE-2026-77205 Patches",
"tags": [
"patch"
],
"url": "https://libreswan.org/security/CVE-2026-77205/"
},
{
"name": "Related: CVE-2026-14957 (incorrect fix being corrected)",
"tags": [
"related"
],
"url": "https://libreswan.org/security/CVE-2026-14957/CVE-2026-14957.txt"
}
],
"solutions": [
{
"lang": "en",
"value": "Upgrade to libreswan 5.3.3 or later. Patches are available at https://libreswan.org/security/CVE-2026-77205/"
}
],
"source": {
"defects": [
"CVE-2026-77205"
],
"discovery": "EXTERNAL"
},
"taxonomyMappings": [
{
"taxonomyName": "ATT\u0026CK",
"taxonomyRelations": [
{
"relationshipName": "maps to",
"relationshipValue": "Application or System Exploitation (DoS)",
"taxonomyId": "T1499.004"
}
],
"taxonomyVersion": "15.1"
}
],
"timeline": [
{
"lang": "en",
"time": "2026-07-30T00:00:00.000Z",
"value": "Libreswan was notified of the issue via security@libreswan.org"
},
{
"lang": "en",
"time": "2026-09-24T00:00:00.000Z",
"value": "Advanced notice given to supported customers and distributions"
},
{
"lang": "en",
"time": "2026-10-05T00:00:00.000Z",
"value": "Public announcement and release of libreswan 5.3.3"
}
],
"title": "Denial of Service via sending bogus X.509 certificates",
"workarounds": [
{
"lang": "en",
"value": "Disabling FIPS mode will prevent this attack vector. If this is not possible, upgrade to a later libreswan version or apply the available patch."
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "d42dc95b-23f1-4e06-9076-20753a0fb0df",
"assignerShortName": "libreswan",
"cveId": "CVE-2026-77205",
"datePublished": "2026-10-13T21:28:03.390Z",
"dateReserved": "2026-08-20T18:13:09.377Z",
"dateUpdated": "2026-10-16T15:31:54.457Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-77205",
"date": "2026-10-29",
"epss": "0.00183",
"percentile": "0.07889"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"collectionURL": "https://github.com/libreswan/libreswan",
"defaultStatus": "unaffected",
"packageName": "libreswan",
"product": "libreswan",
"programRoutines": [
{
"name": "add_decoded_cert"
}
],
"repo": "https://github.com/libreswan/libreswan",
"vendor": "The Libreswan Project",
"versions": [
{
"lessThanOrEqual": "5.3.2",
"status": "affected",
"version": "5.3",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "5.3.3",
"versionType": "semver"
}
]
}
],
"source": "d42dc95b-23f1-4e06-9076-20753a0fb0df"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Libreswan in FIPS mode has a vulnerability where badly formed received certificates are rejected, but not deleted from the NSS cache. As a result, any real certificates with the same serial number are rejected as well. This can be abused to lock out legitimate peers from connecting. The add_decoded_cert() function missed a call to CERT_DestroyCertificate() due to an incorrect fix for CVE-2026-14957. Sending bogus certificates with new serial numbers could prevent the real certificates with those serial numbers from connecting until the service has restarted."
}
],
"id": "CVE-2026-77205",
"lastModified": "2026-10-16T19:55:59.740",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 3.7,
"baseSeverity": "LOW",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L",
"version": "3.1"
},
"exploitabilityScore": 2.2,
"impactScore": 1.4,
"source": "d42dc95b-23f1-4e06-9076-20753a0fb0df",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-77205",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-16T15:14:28.040688Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-10-13T22:18:24.577",
"references": [
{
"source": "d42dc95b-23f1-4e06-9076-20753a0fb0df",
"url": "https://libreswan.org/security/CVE-2026-14957/CVE-2026-14957.txt"
},
{
"source": "d42dc95b-23f1-4e06-9076-20753a0fb0df",
"url": "https://libreswan.org/security/CVE-2026-77205/"
},
{
"source": "d42dc95b-23f1-4e06-9076-20753a0fb0df",
"url": "https://libreswan.org/security/CVE-2026-77205/CVE-2026-77205.txt"
}
],
"sourceIdentifier": "d42dc95b-23f1-4e06-9076-20753a0fb0df",
"vulnStatus": "Awaiting Analysis",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-772"
}
],
"source": "d42dc95b-23f1-4e06-9076-20753a0fb0df",
"type": "Secondary"
}
]
}
},
"redhat_vex": {
"aggregate_severity": "Low",
"current_release_date": "2026-10-26T13:53:19+00:00",
"cve": "CVE-2026-77205",
"id": "CVE-2026-77205",
"initial_release_date": "2026-10-05T00:00:00+00:00",
"product_status:fixed": "17",
"product_status:known_affected": "3",
"product_status:known_not_affected": "9",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "libreswan: Denial of Service via sending bogus X.509 certificates",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-77205.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "low",
"current_release_date": "2026-10-28T00:49:54Z",
"cve": "CVE-2026-77205",
"id": "CVE-2026-77205",
"initial_release_date": "2026-10-28T00:49:54Z",
"product_status:recommended": "2",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-77205",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-77205.json",
"version": "2"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.