Quick answers
- Is CVE-2026-42285 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42285 being exploited in the wild.
- How severe is CVE-2026-42285?
- High severity, with a CVSS score of 7.5, published 7 May 2026.
- Which products and versions are affected?
- github.com/osrg/gobgp/v4 (Go) SEMVER:introduced=4.4.0,fixed=4.5.0.
- Is there a fix for CVE-2026-42285?
- Yes. github.com/osrg/gobgp/v4 (Go): upgrade to 4.5.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42285 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-42285?
- 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.5.0 or later
go get github.com/osrg/gobgp/v4@v4.5.0
Technical details
A nil pointer dereference exists in GoBGP version 4.4.0 within the AdjRib.Update function. The vulnerability is triggered when the server receives a BGP UPDATE message containing inconsistent attribute lengths. While the software correctly identifies the malformed attributes and attempts to treat the message as a 'withdraw' action, it fails to properly manage the internal state transition, leading to a nil pointer access in internal/pkg/table/adj.go. An unauthenticated remote peer can exploit this over the network to cause a fatal panic (SIGSEGV), resulting in a complete denial of service. This issue is resolved in version 4.5.0.
Affected products
- osrg GoBGP 4.4.0
Identifiers
- CVE-2026-42285
- GHSA-p3w2-64xm-833j
- GO-2026-5525
Timeline
- 2026-04-30: patched: Fixed in version 4.5.0
- 2026-05-07: disclosed: Public disclosure of CVE-2026-42285