Is CVE-2026-37461 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-37461 being exploited in the wild.

How severe is CVE-2026-37461?

High severity, with a CVSS score of 7.5, published 4 May 2026.

Which products and versions are affected?

github.com/osrg/gobgp/v4 (Go) SEMVER:introduced=0,fixed=4.4.0.

Is there a fix for CVE-2026-37461?

Yes. github.com/osrg/gobgp/v4 (Go): upgrade to 4.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-37461 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-37461?

Check whether you run github.com/osrg/gobgp/v4 (Go) or Osrg Gobgp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-37461: osrg GoBGP out-of-bounds read and underflow in BGP UPDATE parsing

CVE-2026-37461 · Severity: high · CVSS 7.5 · Published 2026-05-04

GoBGP is an open-source implementation of the Border Gateway Protocol (BGP) used to manage how data is routed across the internet. A vulnerability in how it processes specific network update messages could allow an attacker to crash the service. This results in a denial-of-service (DoS) condition, potentially disrupting network routing and connectivity for organizations relying on this software.

Technologies: github.com/osrg/gobgp/v4 (Go), Osrg Gobgp. Vendors: Go, Osrg.

Quick answers

Is CVE-2026-37461 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-37461 being exploited in the wild.
How severe is CVE-2026-37461?: High severity, with a CVSS score of 7.5, published 4 May 2026.
Which products and versions are affected?: github.com/osrg/gobgp/v4 (Go) SEMVER:introduced=0,fixed=4.4.0.
Is there a fix for CVE-2026-37461?: Yes. github.com/osrg/gobgp/v4 (Go): upgrade to 4.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-37461 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-37461?: Check whether you run github.com/osrg/gobgp/v4 (Go) or Osrg Gobgp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/osrg/gobgp/v4 (Go): upgrade to 4.4.0 or later
```
go get github.com/osrg/gobgp/v4@v4.4.0
```

Technical details

Two related issues in GoBGP v4.3.0 contribute to potential instability. First, the 'ParseIP6Extended' function in 'bgp.go' performs an insufficient length check, validating only 8 bytes when 20 bytes are required for IPv6 extended community parsing, leading to an out-of-bounds read. Second, the 'DecodeFromBytes' function in 'BGPUpdate' is susceptible to a uint16 underflow when processing malformed UPDATE messages that declare section lengths smaller than the actual encoded elements. An unauthenticated remote attacker can exploit these flaws by sending specially crafted BGP UPDATE messages to trigger a crash (Denial of Service). Patches have been developed to enforce proper bounds checking and prevent integer wrapping.

Affected products

osrg GoBGP 4.3.0

Identifiers

CVE-2026-37461
GHSA-wmvj-f67g-qg4g
GO-2026-5713

Timeline

2026-05-04: disclosed
2026-05-04: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.