https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-05T15:14:07.319296+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-15300 bdu:2026-15300 2026-10-05T15:14:07.322153+00:00 bdu:2026-15300 https://cve.radiocsirt.org/vuln/euvd-2026-308938 EUVD-2026-308938 2026-10-05T15:14:07.322185+00:00 EUVD-2026-308938 https://cve.radiocsirt.org/vuln/fkie_cve-2026-41642 fkie_cve-2026-41642 2026-10-05T15:14:07.322199+00:00

GoBGP is an open source Border Gateway Protocol (BGP) implementation in the Go Programming Language. In version 4.3.0, a remote Denial of Service (DoS) vulnerability exists in GoBGP due to a nil pointer dereference. When a malformed BGP UPDATE message contains an unrecognized Path Attribute marked as "Well-known," the daemon fails to interrupt the message handling flow. This results in an illegal memory access and a full process crash (panic). This issue has been patched in version 4.4.0.

 https://cve.radiocsirt.org/vuln/ghsa-7235-89m6-f4px GHSA-7235-89m6-f4px — GoBGP has Remote Denial of Service (Panic) via Malformed Well-known Path Attribute 2026-10-05T15:14:07.322229+00:00

Affected: Go: github.com/osrg/gobgp/v4

### Summary A remote Denial of Service (DoS) vulnerability exists in GoBGP due to a nil pointer dereference. When a malformed BGP UPDATE message contains an unrecognized Path Attribute marked as "Well-known," the daemon fails to interrupt the message handling flow. This results in an illegal memory access and a full process crash (panic).

### Details The vulnerability is located in the Finite State Machine (FSM) message handling loop in pkg/server/fsm.go. According to RFC 4271, any Path Attribute with the Optional bit set to 0 is treated as "Well-known." If the Type Code is unrecognized, the BGP speaker MUST send a NOTIFICATION message.

In GoBGP v4.3.0, when such an attribute (e.g., Type 0xEE or 0xFF with flags 0x40) is received, the parsing layer identifies the error. However, the logic in recvMessageloop (around Line 1826) does not properly halt execution. It proceeds to reference the body of the parsed message. Because the message was deemed invalid during the initial attribute check, the body pointer is nil, leading to: panic: runtime error: invalid memory address or nil pointer dereference.

This bypasses the intended error-handling mechanism and causes the entire BGP daemon to terminate, rather than just closing the affected session.

``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xc225e4]

goroutine 50 [running]: github.com/osrg/gobgp/v4/pkg/server.(*fsmHandler).recvMessagelo…

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-41642 Withdrawn: UBUNTU-CVE-2026-41642 2026-10-05T15:14:07.322308+00:00

Withdrawn by the publisher.

Affected: Ubuntu:Pro:18.04:LTS: gobgp, Ubuntu:Pro:20.04:LTS: gobgp, Ubuntu:Pro:22.04:LTS: gobgp, Ubuntu:Pro:24.04:LTS: gobgp, Ubuntu:25.10: gobgp, Ubuntu:Pro:26.04:LTS: gobgp

GoBGP is an open source Border Gateway Protocol (BGP) implementation in the Go Programming Language. In version 4.3.0, a remote Denial of Service (DoS) vulnerability exists in GoBGP due to a nil pointer dereference. When a malformed BGP UPDATE message contains an unrecognized Path Attribute marked as "Well-known," the daemon fails to interrupt the message handling flow. This results in an illegal memory access and a full process crash (panic). This issue has been patched in version 4.4.0.