CVE-2026-129217: bgpd: out-of-bounds heap read and crash on NOTIFICATION Cease/Hard Reset with one data byte

Published Nov 13, 2026
·
Updated

In FRRouting (FRR) 8.3 through 10.5.1, bgpnotifydecapsulatehardreset() in bgpd/bgppacket.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.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.6.0

Event History

Nov 13, 2026
CVE Published
via MITRE·07:06 PM
Data Sourced
via MITRE·07:06 PM
RemedyDescriptionWeakness

Frequently Asked Questions

1

Which deployments are exposed to this denial of service?

FRR deployments running bgpd versions 8.3 through 10.5.1 are affected if a remote BGP peer can establish a session and Graceful Restart is negotiated with the Notification (N) bit. An unauthenticated Internet host that cannot establish such a BGP session is not described as able to trigger the issue.

2

What does an attacker need to send to trigger the crash?

The peer must send a BGP NOTIFICATION message with Cease/Hard Reset semantics whose data field is exactly one byte long. This causes an underflowed encapsulated-data length and an out-of-bounds heap read, followed by an assertion failure in bgpd.

3

What is the operational impact if exploitation succeeds?

The bgpd daemon crashes, terminating all BGP sessions. The described impact is denial of service rather than route manipulation or disclosure.

4

Which releases contain fixes?

Fixed releases are 10.0.5, 10.1.5, 10.2.6, 10.3.4, 10.4.3, 10.5.2, and 10.6.0.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203