Search
Find a vulnerability
Search criteria
5 vulnerabilities
CVE-2026-129456 (GCVE-0-2026-129456)
Vulnerability from cvelistv5 – Published: 2026-11-14 19:13 – Updated: 2026-11-15 18:05
VLAI
EPSS
VEX
Title
frr: bgpd use-after-free of Tunnel Encapsulation sub-TLVs via the attribute intern reuse cache with soft-reconfiguration inbound
Summary
In FRRouting, bgpd frees the sub-TLV chain of a Tunnel Encapsulation attribute (type 23) while routes stored by bgpd still point to it, if the attribute is received from a neighbor that has "soft-reconfiguration inbound" configured. A cache added to speed up attribute interning while processing the prefixes of an UPDATE checks whether an interned attribute set may be reused by comparing the parsed attributes with themselves, so the check always succeeds. Interning the parsed attributes for the Adj-RIB-In removes the Tunnel Encapsulation sub-TLVs from them, and the copy that bgpd then interns for the route reuses the cached attribute set, which still holds the sub-TLVs, without taking a reference on them. When the route is later replaced, withdrawn or cleared, for example when the session goes down, the sub-TLV chain is freed while still in use, and bgpd then reads it, decrements a reference count inside it and frees it a second time. In the reporter's build without AddressSanitizer this ended in an assertion failure in bgpd's memory accounting, aborting bgpd and dropping all BGP sessions on the router, and the neighbor can repeat it each time bgpd restarts. Because freed heap memory is written to and freed again, consequences beyond a crash cannot be ruled out. An established BGP session is required, and the attribute does not need to be malformed. bgpd processes attribute 23 from every neighbor, including eBGP neighbors, unless it is explicitly discarded, although RFC 9012 requires it to be filtered on eBGP sessions by default. Neighbors without "soft-reconfiguration inbound" are not affected.
Severity
CWE
References
3 references
| URL | Tags |
|---|---|
| https://github.com/FRRouting/frr/issues/20874 | issue-tracking |
| https://github.com/FRRouting/frr/pull/22008/chang… | patch |
| https://github.com/FRRouting/frr/commit/5c2410567… | patch |
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"modules": [
"bgpd"
],
"product": "frrouting",
"programFiles": [
"bgpd/bgp_attr.c"
],
"programRoutines": [
{
"name": "bgp_attr_intern"
},
{
"name": "encap_unintern"
}
],
"repo": "https://github.com/FRRouting/frr/",
"vendor": "frrouting",
"versions": [
{
"changes": [
{
"at": "40f25e62686865649b7631ec30756f9661e12dd3",
"status": "unaffected"
}
],
"lessThan": "*",
"status": "affected",
"version": "97dd9ea9e3e2aa982dcbc36466573eb4c0c87cbd",
"versionType": "git"
},
{
"lessThan": "10.6.2",
"status": "affected",
"version": "10.6.0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*",
"versionEndExcluding": "10.6.2",
"versionStartIncluding": "10.6.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Fault Chain (https://faultchain.com/)"
},
{
"lang": "en",
"type": "reporter",
"value": "Bronson Yen \u003cbronson@calif.io\u003e"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Mark Stapp \u003cmjs@cisco.com\u003e"
}
],
"descriptions": [
{
"lang": "en",
"value": "In FRRouting, bgpd frees the sub-TLV chain of a Tunnel Encapsulation attribute (type 23) while routes stored by bgpd still point to it, if the attribute is received from a neighbor that has \"soft-reconfiguration inbound\" configured. A cache added to speed up attribute interning while processing the prefixes of an UPDATE checks whether an interned attribute set may be reused by comparing the parsed attributes with themselves, so the check always succeeds. Interning the parsed attributes for the Adj-RIB-In removes the Tunnel Encapsulation sub-TLVs from them, and the copy that bgpd then interns for the route reuses the cached attribute set, which still holds the sub-TLVs, without taking a reference on them. When the route is later replaced, withdrawn or cleared, for example when the session goes down, the sub-TLV chain is freed while still in use, and bgpd then reads it, decrements a reference count inside it and frees it a second time. In the reporter\u0027s build without AddressSanitizer this ended in an assertion failure in bgpd\u0027s memory accounting, aborting bgpd and dropping all BGP sessions on the router, and the neighbor can repeat it each time bgpd restarts. Because freed heap memory is written to and freed again, consequences beyond a crash cannot be ruled out. An established BGP session is required, and the attribute does not need to be malformed. bgpd processes attribute 23 from every neighbor, including eBGP neighbors, unless it is explicitly discarded, although RFC 9012 requires it to be filtered on eBGP sessions by default. Neighbors without \"soft-reconfiguration inbound\" are not affected."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NO",
"Recovery": "AUTOMATIC",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 7.7,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "LOW",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:L/AU:N/R:A",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-416",
"description": "CWE-416 Use After Free: the attribute intern reuse cache returns an interned attribute set holding the Tunnel Encapsulation sub-TLV chain without taking a reference on the chain, which is then freed while still referenced and later accessed by encap_unintern()",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-415",
"description": "CWE-415 Double Free",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-15T18:05:07.191Z",
"orgId": "57a55968-44ac-464c-a794-6ba3baad09c4",
"shortName": "NetDEF"
},
"references": [
{
"tags": [
"issue-tracking"
],
"url": "https://github.com/FRRouting/frr/issues/20874"
},
{
"tags": [
"patch"
],
"url": "https://github.com/FRRouting/frr/pull/22008/changes/40f25e62686865649b7631ec30756f9661e12dd3"
},
{
"tags": [
"patch"
],
"url": "https://github.com/FRRouting/frr/commit/5c241056777b27b209bc89326f0061ec6d5e0924"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "frr: bgpd use-after-free of Tunnel Encapsulation sub-TLVs via the attribute intern reuse cache with soft-reconfiguration inbound",
"workarounds": [
{
"lang": "en",
"value": "Remove \"neighbor \u003cneighbor\u003e soft-reconfiguration inbound\", or configure \"neighbor \u003cneighbor\u003e path-attribute discard 23\" (or \"neighbor \u003cneighbor\u003e path-attribute treat-as-withdraw 23\") for neighbors that are not expected to send the Tunnel Encapsulation attribute, in particular all eBGP neighbors. With the attribute discarded, bgpd skips it without parsing or storing it."
}
],
"x_generator": {
"engine": "vim"
}
}
},
"cveMetadata": {
"assignerOrgId": "57a55968-44ac-464c-a794-6ba3baad09c4",
"assignerShortName": "NetDEF",
"cveId": "CVE-2026-129456",
"datePublished": "2026-11-14T19:13:23.983Z",
"dateReserved": "2026-11-14T19:03:34.352Z",
"dateUpdated": "2026-11-15T18:05:07.191Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-129217 (GCVE-0-2026-129217)
Vulnerability from cvelistv5 – Published: 2026-11-13 19:06 – Updated: 2026-11-13 19:06
VLAI
EPSS
VEX
Title
bgpd: out-of-bounds heap read and crash on NOTIFICATION Cease/Hard Reset with one data byte
Summary
In FRRouting (FRR) 8.3 through 10.5.1, bgp_notify_decapsulate_hard_reset() in bgpd/bgp_packet.c does not validate the length of the data field of a received BGP NOTIFICATION Cease/Hard Reset message (RFC 8538). When the data field is exactly one byte long, the function reads one byte past the end of a heap buffer and the 16-bit length of the encapsulated data underflows to 65535, causing a 65535-byte out-of-bounds heap read followed by an assertion failure. A remote BGP peer that has established a session and negotiated the Graceful Restart capability with the Notification (N) bit can send such a message to crash the bgpd daemon, terminating all BGP sessions (denial of service). This is fixed in 10.0.5, 10.1.5, 10.2.6, 10.3.4, 10.4.3, 10.5.2 and 10.6.0.
Severity
References
2 references
| URL | Tags |
|---|---|
| https://github.com/FRRouting/frr/issues/20793 | issue-tracking |
| https://github.com/FRRouting/frr/pull/20796 | patch |
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"modules": [
"bgpd"
],
"product": "FRRouting",
"programFiles": [
"bgpd/bgp_packet.c"
],
"programRoutines": [
{
"name": "bgp_notify_decapsulate_hard_reset()"
}
],
"repo": "https://github.com/frrouting/frr.git",
"vendor": "FRRouting",
"versions": [
{
"lessThan": "10.5.2",
"status": "affected",
"version": "10.5.0",
"versionType": "semver"
},
{
"lessThan": "10.4.3",
"status": "affected",
"version": "10.4.0",
"versionType": "semver"
},
{
"lessThan": "10.3.4",
"status": "affected",
"version": "10.3",
"versionType": "custom"
},
{
"lessThan": "10.2.6",
"status": "affected",
"version": "10.2",
"versionType": "custom"
},
{
"lessThan": "10.1.5",
"status": "affected",
"version": "10.1",
"versionType": "custom"
},
{
"lessThan": "10.0.5",
"status": "affected",
"version": "8.3",
"versionType": "custom"
},
{
"lessThan": "8.3",
"status": "unaffected",
"version": "0",
"versionType": "custom"
}
]
}
],
"configurations": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "bgpd must be running with at least one BGP neighbor (or dynamic listen range) through which the attacker can establish a session, and the Graceful Restart capability with the Notification (N) bit must be negotiated in the OPEN exchange with that peer. This is the default configuration: \"bgp graceful-restart notification\" is enabled by default since FRR 8.3 and the Graceful Restart capability is advertised by default (helper mode). Instances configured with \"no bgp graceful-restart notification\" or \"bgp graceful-restart-disable\" are not affected."
}
],
"value": "bgpd must be running with at least one BGP neighbor (or dynamic listen range) through which the attacker can establish a session, and the Graceful Restart capability with the Notification (N) bit must be negotiated in the OPEN exchange with that peer. This is the default configuration: \"bgp graceful-restart notification\" is enabled by default since FRR 8.3 and the Graceful Restart capability is advertised by default (helper mode). Instances configured with \"no bgp graceful-restart notification\" or \"bgp graceful-restart-disable\" are not affected."
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Fault Chain (https://faultchain.com/)"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "In FRRouting (FRR) 8.3 through 10.5.1, bgp_notify_decapsulate_hard_reset() in bgpd/bgp_packet.c does not validate the length of the data field of a received BGP NOTIFICATION Cease/Hard Reset message (RFC 8538). When the data field is exactly one byte long, the function reads one byte past the end of a heap buffer and the 16-bit length of the encapsulated data underflows to 65535, causing a 65535-byte out-of-bounds heap read followed by an assertion failure. A remote BGP peer that has established a session and negotiated the Graceful Restart capability with the Notification (N) bit can send such a message to crash the bgpd daemon, terminating all BGP sessions (denial of service). This is fixed in 10.0.5, 10.1.5, 10.2.6, 10.3.4, 10.4.3, 10.5.2 and 10.6.0."
}
],
"value": "In FRRouting (FRR) 8.3 through 10.5.1, bgp_notify_decapsulate_hard_reset() in bgpd/bgp_packet.c does not validate the length of the data field of a received BGP NOTIFICATION Cease/Hard Reset message (RFC 8538). When the data field is exactly one byte long, the function reads one byte past the end of a heap buffer and the 16-bit length of the encapsulated data underflows to 65535, causing a 65535-byte out-of-bounds heap read followed by an assertion failure. A remote BGP peer that has established a session and negotiated the Graceful Restart capability with the Notification (N) bit can send such a message to crash the bgpd daemon, terminating all BGP sessions (denial of service). This is fixed in 10.0.5, 10.1.5, 10.2.6, 10.3.4, 10.4.3, 10.5.2 and 10.6.0."
}
],
"impacts": [
{
"capecId": "CAPEC-540",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-540 Overread Buffers"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "HIGH",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 6,
"baseSeverity": "MEDIUM",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "HIGH",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-125",
"description": "CWE-125 Out-of-bounds read",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-191",
"description": "CWE-191 Integer underflow (wrap or wraparound)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-13T19:06:40.219Z",
"orgId": "57a55968-44ac-464c-a794-6ba3baad09c4",
"shortName": "NetDEF"
},
"references": [
{
"tags": [
"issue-tracking"
],
"url": "https://github.com/FRRouting/frr/issues/20793"
},
{
"tags": [
"patch"
],
"url": "https://github.com/FRRouting/frr/pull/20796"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Upgrade to a fixed version of FRRouting"
}
],
"value": "Upgrade to a fixed version of FRRouting"
}
],
"source": {
"discovery": "UNKNOWN"
},
"timeline": [
{
"lang": "en",
"time": "2026-02-12T07:59:00.000Z",
"value": "Github Issue opened (no responsible disclosure)"
}
],
"title": "bgpd: out-of-bounds heap read and crash on NOTIFICATION Cease/Hard Reset with one data byte",
"workarounds": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Graceful Restart Capability needs to be enabled. Disable the Capability with\u0026nbsp;\"no bgp graceful-restart notification\"\u0026nbsp;or \"bgp graceful-restart-disable\""
}
],
"value": "Graceful Restart Capability needs to be enabled. Disable the Capability with\u00a0\"no bgp graceful-restart notification\"\u00a0or \"bgp graceful-restart-disable\""
}
],
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "57a55968-44ac-464c-a794-6ba3baad09c4",
"assignerShortName": "NetDEF",
"cveId": "CVE-2026-129217",
"datePublished": "2026-11-13T19:06:40.219Z",
"dateReserved": "2026-11-13T19:02:49.870Z",
"dateUpdated": "2026-11-13T19:06:40.219Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-120221 (GCVE-0-2026-120221)
Vulnerability from cvelistv5 – Published: 2026-11-13 11:54 – Updated: 2026-11-14 14:55
VLAI
EPSS
VEX
Title
frr: bgpd double free of peer-group Site-of-Origin when dynamic neighbors disconnect
Summary
In FRRouting, bgpd frees the same memory twice when dynamic BGP neighbors disconnect, if the peer-group used by a "bgp listen range" also has a Site-of-Origin configured ("neighbor PG soo"). Each dynamic neighbor shares the peer-group's SoO value instead of getting its own copy, but frees it as its own when the neighbor is deleted, which happens as soon as its connection closes. The first disconnect leaves the peer-group pointing at freed memory, and the second disconnect frees it again, causing bgpd to abort and drop all BGP sessions on the router. Any host whose address falls inside the listen range can trigger this by opening and closing two TCP connections to the BGP port, without sending any BGP message and without knowing the AS number, and can repeat it each time bgpd restarts. If the peer-group has a TCP-MD5 password, only hosts that know the password can trigger it. Two ordinary flaps of legitimate dynamic neighbors have the same effect. Between the two frees, displaying the configuration ("show running-config") or establishing a dynamic neighbor also reads the freed memory, which can crash bgpd after a single disconnect. Only configurations that combine a listen range with a SoO on the same peer-group are affected.
Severity
CWE
References
1 reference
| URL | Tags |
|---|---|
| https://github.com/FRRouting/frr/pull/21685/chang… | patch |
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| frrouting | frrouting |
Affected:
01da2d26911c72023e71579bf4feeb707087ef50 , < *
(git)
Affected: 8.4.0 , < 10.2.7 (semver) Affected: 10.3.0 , < 10.3.5 (semver) Affected: 10.4.0 , < 10.4.6 (semver) Affected: 10.5.0 , < 10.5.6 (semver) Affected: 10.6.0 , < 10.6.3 (semver) Affected: 10.7.0 , < 10.7.2 (semver) cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"modules": [
"bgpd"
],
"product": "frrouting",
"programFiles": [
"bgpd/bgpd.c"
],
"programRoutines": [
{
"name": "peer_group2peer_config_copy_af"
},
{
"name": "peer_delete"
}
],
"repo": "https://github.com/FRRouting/frr/",
"vendor": "frrouting",
"versions": [
{
"changes": [
{
"at": "6a96f515760dc278147fbf802777956ba80c7edd",
"status": "unaffected"
}
],
"lessThan": "*",
"status": "affected",
"version": "01da2d26911c72023e71579bf4feeb707087ef50",
"versionType": "git"
},
{
"lessThan": "10.2.7",
"status": "affected",
"version": "8.4.0",
"versionType": "semver"
},
{
"lessThan": "10.3.5",
"status": "affected",
"version": "10.3.0",
"versionType": "semver"
},
{
"lessThan": "10.4.6",
"status": "affected",
"version": "10.4.0",
"versionType": "semver"
},
{
"lessThan": "10.5.6",
"status": "affected",
"version": "10.5.0",
"versionType": "semver"
},
{
"lessThan": "10.6.3",
"status": "affected",
"version": "10.6.0",
"versionType": "semver"
},
{
"lessThan": "10.7.2",
"status": "affected",
"version": "10.7.0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*",
"versionEndExcluding": "10.2.7",
"versionStartIncluding": "8.4.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*",
"versionEndExcluding": "10.3.5",
"versionStartIncluding": "10.3.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*",
"versionEndExcluding": "10.4.6",
"versionStartIncluding": "10.4.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*",
"versionEndExcluding": "10.5.6",
"versionStartIncluding": "10.5.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*",
"versionEndExcluding": "10.6.3",
"versionStartIncluding": "10.6.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*",
"versionEndExcluding": "10.7.2",
"versionStartIncluding": "10.7.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Nageswara Soma \u003cnsoma@cisco.com\u003e (not reported as security issue)"
},
{
"lang": "en",
"type": "tool",
"value": "Anthropic OSS-scanner (re-report, ANT-2026-X4QI9LP4)"
}
],
"descriptions": [
{
"lang": "en",
"value": "In FRRouting, bgpd frees the same memory twice when dynamic BGP neighbors disconnect, if the peer-group used by a \"bgp listen range\" also has a Site-of-Origin configured (\"neighbor PG soo\"). Each dynamic neighbor shares the peer-group\u0027s SoO value instead of getting its own copy, but frees it as its own when the neighbor is deleted, which happens as soon as its connection closes. The first disconnect leaves the peer-group pointing at freed memory, and the second disconnect frees it again, causing bgpd to abort and drop all BGP sessions on the router. Any host whose address falls inside the listen range can trigger this by opening and closing two TCP connections to the BGP port, without sending any BGP message and without knowing the AS number, and can repeat it each time bgpd restarts. If the peer-group has a TCP-MD5 password, only hosts that know the password can trigger it. Two ordinary flaps of legitimate dynamic neighbors have the same effect. Between the two frees, displaying the configuration (\"show running-config\") or establishing a dynamic neighbor also reads the freed memory, which can crash bgpd after a single disconnect. Only configurations that combine a listen range with a SoO on the same peer-group are affected."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NO",
"Recovery": "AUTOMATIC",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 8.2,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "LOW",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:N/R:A",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-415",
"description": "CWE-415 Double Free",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-416",
"description": "CWE-416 Use After Free: the peer-group\u0027s SoO pointer is left dangling after the first dynamic neighbor is deleted and is read by later neighbors and by the configuration writer",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-14T14:55:45.546Z",
"orgId": "57a55968-44ac-464c-a794-6ba3baad09c4",
"shortName": "NetDEF"
},
"references": [
{
"tags": [
"patch"
],
"url": "https://github.com/FRRouting/frr/pull/21685/changes/6a96f515760dc278147fbf802777956ba80c7edd"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "frr: bgpd double free of peer-group Site-of-Origin when dynamic neighbors disconnect",
"workarounds": [
{
"lang": "en",
"value": "Do not configure \"neighbor \u003cpeer-group\u003e soo\" on a peer-group used by \"bgp listen range\". Instead, set the SoO extended community with an inbound route-map, or set \"neighbor soo\" on statically configured neighbors. Configuring a TCP-MD5 \"password\" on the peer-group limits the trigger to hosts that know the key."
}
],
"x_generator": {
"engine": "vim"
}
}
},
"cveMetadata": {
"assignerOrgId": "57a55968-44ac-464c-a794-6ba3baad09c4",
"assignerShortName": "NetDEF",
"cveId": "CVE-2026-120221",
"datePublished": "2026-11-13T11:54:24.035Z",
"dateReserved": "2026-10-31T18:17:02.102Z",
"dateUpdated": "2026-11-14T14:55:45.546Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-120033 (GCVE-0-2026-120033)
Vulnerability from cvelistv5 – Published: 2026-11-12 18:07 – Updated: 2026-11-14 14:46
VLAI
EPSS
VEX
Title
frr: bgpd Send Hold Timer expiry bypasses the FSM, leaving a phantom Established session or crashing bgpd with Graceful Restart
Summary
In FRRouting, bgpd does not correctly close a BGP session when the Send Hold Timer (RFC 9687) expires, i.e. when a neighbor has stopped accepting data from the router for twice the hold time. The connection is closed, but bgpd still considers the session to be up. A BGP neighbor that keeps sending KEEPALIVEs but stops reading from its connection, at a time when the router has a large amount of data to send to it (for example while sending it a full routing table), can trigger this. If the neighbor announced Graceful Restart support, bgpd crashes shortly after the session is closed, taking down all BGP sessions on the router, and the neighbor can repeat this each time bgpd restarts. Otherwise, the session stays stuck in the Established state: the neighbor's routes stay installed and keep being advertised to other peers, and the neighbor cannot reconnect until an operator clears the session manually. The neighbor does not need to be malicious; an overloaded or stuck peer can trigger the same behavior. No special configuration is required: any established BGP neighbor can trigger the issue, and Graceful Restart helper mode, which leads to the crash, is enabled by default.
Severity
CWE
References
1 reference
| URL | Tags |
|---|---|
| https://github.com/FRRouting/frr/pull/23945/chang… | patch |
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| frrouting | frrouting |
Affected:
4967bf6d729d7dd14dff7b672b2fd4afe78a0d86 , < *
(git)
Affected: 10.1.0 , < 10.4.6 (semver) Affected: 10.5.0 , < 10.5.6 (semver) Affected: 10.6.0 , < 10.6.3 (semver) Affected: 10.7.0 , < 10.7.2 (semver) cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:* |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"modules": [
"bgpd"
],
"product": "frrouting",
"programFiles": [
"bgpd/bgp_fsm.c"
],
"programRoutines": [
{
"name": "bgp_event_stop_with_notify"
}
],
"repo": "https://github.com/FRRouting/frr/",
"vendor": "frrouting",
"versions": [
{
"changes": [
{
"at": "57a7f3eb48837359d6e3ee5ebd4acea8f49320e5",
"status": "unaffected"
}
],
"lessThan": "*",
"status": "affected",
"version": "4967bf6d729d7dd14dff7b672b2fd4afe78a0d86",
"versionType": "git"
},
{
"lessThan": "10.4.6",
"status": "affected",
"version": "10.1.0",
"versionType": "semver"
},
{
"lessThan": "10.5.6",
"status": "affected",
"version": "10.5.0",
"versionType": "semver"
},
{
"lessThan": "10.6.3",
"status": "affected",
"version": "10.6.0",
"versionType": "semver"
},
{
"lessThan": "10.7.2",
"status": "affected",
"version": "10.7.0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*",
"versionEndExcluding": "10.4.6",
"versionStartIncluding": "10.1.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*",
"versionEndExcluding": "10.5.6",
"versionStartIncluding": "10.5.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*",
"versionEndExcluding": "10.6.3",
"versionStartIncluding": "10.6.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*",
"versionEndExcluding": "10.7.2",
"versionStartIncluding": "10.7.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Srinivasan Koona Lokabiraman \u003csrinivasan@nexthop.ai\u003e (not reported as security issue)"
},
{
"lang": "en",
"type": "tool",
"value": "Anthropic OSS-scanner (re-report, ANT-2026-GSLEN9XB)"
}
],
"descriptions": [
{
"lang": "en",
"value": "In FRRouting, bgpd does not correctly close a BGP session when the Send Hold Timer (RFC 9687) expires, i.e. when a neighbor has stopped accepting data from the router for twice the hold time. The connection is closed, but bgpd still considers the session to be up. A BGP neighbor that keeps sending KEEPALIVEs but stops reading from its connection, at a time when the router has a large amount of data to send to it (for example while sending it a full routing table), can trigger this. If the neighbor announced Graceful Restart support, bgpd crashes shortly after the session is closed, taking down all BGP sessions on the router, and the neighbor can repeat this each time bgpd restarts. Otherwise, the session stays stuck in the Established state: the neighbor\u0027s routes stay installed and keep being advertised to other peers, and the neighbor cannot reconnect until an operator clears the session manually. The neighbor does not need to be malicious; an overloaded or stuck peer can trigger the same behavior. No special configuration is required: any established BGP neighbor can trigger the issue, and Graceful Restart helper mode, which leads to the crash, is enabled by default."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NO",
"Recovery": "AUTOMATIC",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 6,
"baseSeverity": "MEDIUM",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "LOW",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "LOW",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:L/SA:L/AU:N/R:A",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-617",
"description": "CWE-617 Reachable Assertion",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-372",
"description": "CWE-372 Incomplete Internal State Distinction: Send Hold Timer expiry tears down the connection outside the BGP FSM, leaving it in the Established state without a socket",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-14T14:46:55.176Z",
"orgId": "57a55968-44ac-464c-a794-6ba3baad09c4",
"shortName": "NetDEF"
},
"references": [
{
"tags": [
"patch"
],
"url": "https://github.com/FRRouting/frr/pull/23945/changes/57a7f3eb48837359d6e3ee5ebd4acea8f49320e5"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "frr: bgpd Send Hold Timer expiry bypasses the FSM, leaving a phantom Established session or crashing bgpd with Graceful Restart",
"workarounds": [
{
"lang": "en",
"value": "No configuration workaround fully prevents the issue. Monitor bgpd logs for \"has not made any SendQ progress for 2 holdtimes\" and run \"clear bgp \u003cneighbor\u003e\" for the affected neighbor, which raises a real FSM event and recovers the peer (this does not prevent the abort when Graceful Restart was negotiated, if the restart timer fires first)."
}
],
"x_generator": {
"engine": "vim"
}
}
},
"cveMetadata": {
"assignerOrgId": "57a55968-44ac-464c-a794-6ba3baad09c4",
"assignerShortName": "NetDEF",
"cveId": "CVE-2026-120033",
"datePublished": "2026-11-12T18:07:42.693Z",
"dateReserved": "2026-10-30T18:11:52.731Z",
"dateUpdated": "2026-11-14T14:46:55.176Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-119776 (GCVE-0-2026-119776)
Vulnerability from cvelistv5 – Published: 2026-11-04 14:15 – Updated: 2026-11-09 21:11
VLAI
EPSS
VEX
Title
frr: ospf6d fails to enforce all OSPFv3 packets use IPv6 link-local addresses
Summary
In all prior released versions of FRRouting, the OSPFv3 (for IPv6) implementation does not check that OSPFv3 packets have a link-local source address and either a link-local destination or one of the protocol multicast destination groups. This may enable malicious actors to establish OSPFv3 adjacencies from unexpectedly, distant IPv6 hosts. Proper usage of OSPFv3 authentication trailers (RFC 7166, as is best practice) prevents full exploitation of this issue, though may allow a malicious actor to waste CPU on authentication checks.
Note the linked PR #23935 is not sufficient to fix the issue as it only verifies the source address. It is the destination address that must be checked.
Required configuration: The OSPFv3 for IPv6 routing protocol must be running (ospf6d process) and in use (enabled globally with "router ospf6" and on specific interfaces with "ipv6 ospf6 area".)
Workaround: either:
* configure OSPFv3 authentication trailers ("ipv6 ospf6 authentication")
* or ensure through firewall configuration that only packets with link-local or multicast destination addresses are accepted on input for IPv6 protocol 89 (OSPF). Note that checking the source address is insufficient, as some routers may (unexpectedly) forward packets with global-scoped IPv6 destination addresses even if they have link-local source addresses.
Severity
SSVC
Exploitation: none
Automatable: no
Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-09 21:10 UTC
CWE
- CWE-304 - Missing critical step in authentication: protocol interactions should be limited to IPv6 link-local scope
References
3 references
Impacted products
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-119776",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-09T21:10:58.734852Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-09T21:11:30.420Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "affected",
"modules": [
"ospf6d"
],
"product": "frrouting",
"programFiles": [
"ospf6d/ospf6_message.c"
],
"repo": "https://github.com/FRRouting/frr/",
"vendor": "frrouting",
"versions": [
{
"changes": [
{
"at": "eaccfcdb35bce8d94621b06633417ba3fa657f34",
"status": "unaffected"
}
],
"lessThan": "*",
"status": "affected",
"version": "0",
"versionType": "git"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Bing Shui \u003cbingshui@smail.nju.edu.cn\u003e (not reported as security issue)"
},
{
"lang": "en",
"type": "tool",
"value": "Anthropic OSS-scanner (re-report, ANT-2026-N0E1INIV)"
}
],
"descriptions": [
{
"lang": "en",
"value": "In all prior released versions of FRRouting, the OSPFv3 (for IPv6) implementation does not check that OSPFv3 packets have a link-local source address and either a link-local destination or one of the protocol multicast destination groups. This may enable malicious actors to establish OSPFv3 adjacencies from unexpectedly, distant IPv6 hosts. Proper usage of OSPFv3 authentication trailers (RFC 7166, as is best practice) prevents full exploitation of this issue, though may allow a malicious actor to waste CPU on authentication checks.\n\n\nNote the linked PR #23935 is not sufficient to fix the issue as it only verifies the source address. It is the destination address that must be checked.\n\n\nRequired configuration: The OSPFv3 for IPv6 routing protocol must be running (ospf6d process) and in use (enabled globally with\u00a0\"router ospf6\" and on specific interfaces with \"ipv6 ospf6 area\".)\n\n\nWorkaround: either:\n\n * configure OSPFv3 authentication trailers (\"ipv6 ospf6 authentication\")\n * or ensure through firewall configuration that only packets with link-local or multicast destination addresses are accepted on input for IPv6 protocol 89 (OSPF). Note that checking the source address is insufficient, as some routers may (unexpectedly) forward packets with global-scoped IPv6 destination addresses even if they have link-local source addresses."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "YES",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 6.1,
"baseSeverity": "MEDIUM",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N/AU:Y",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-304",
"description": "CWE-304 Missing critical step in authentication: protocol interactions should be limited to IPv6 link-local scope",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-04T16:53:47.660Z",
"orgId": "57a55968-44ac-464c-a794-6ba3baad09c4",
"shortName": "NetDEF"
},
"references": [
{
"tags": [
"patch"
],
"url": "https://github.com/FRRouting/frr/pull/24183/changes/eaccfcdb35bce8d94621b06633417ba3fa657f34"
},
{
"tags": [
"related"
],
"url": "https://github.com/FRRouting/frr/pull/24183"
},
{
"tags": [
"related"
],
"url": "https://github.com/FRRouting/frr/pull/23935"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "frr: ospf6d fails to enforce all OSPFv3 packets use IPv6 link-local addresses",
"workarounds": [
{
"lang": "en",
"value": "Either:\n\n * configure OSPFv3 authentication trailers (\"ipv6 ospf6 authentication\")\n * or ensure through firewall configuration that only packets with link-local or multicast destination addresses are accepted on input for IPv6 protocol 89 (OSPF). Note that checking the source address is insufficient, as some routers may (unexpectedly) forward packets with global-scoped IPv6 destination addresses even if they have link-local source addresses."
}
],
"x_generator": {
"engine": "vim"
}
}
},
"cveMetadata": {
"assignerOrgId": "57a55968-44ac-464c-a794-6ba3baad09c4",
"assignerShortName": "NetDEF",
"cveId": "CVE-2026-119776",
"datePublished": "2026-11-04T14:15:32.391Z",
"dateReserved": "2026-10-30T16:14:17.897Z",
"dateUpdated": "2026-11-09T21:11:30.420Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}