CVE-2026-7737: GoBGP Memory Buffer Vulnerability

github.com/osrg/gobgp/v4 Updated 08 Jul 2026

Summary

07/07/2026
Yes i
Unrated
Not published

CVE-2026-7737: GoBGP has Improper Restriction of Operations within the Bounds of a Memory Buffer in github.com/osrg/gobgp. Affects github.com/osrg/gobgp/v4 versions < 4.4.0. Fixed in 4.4.0. How to fix ↓

Also tracked for

The same CVE-2026-7737 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

GoBGP is an open-source Border Gateway Protocol (BGP) implementation written in Go. It is designed to provide a flexible and efficient way to manage BGP routing in networks. GoBGP supports various features such as route filtering, policy-based routing, and monitoring. However, it is susceptible to vulnerabilities that can compromise its operation, such as improper memory buffer restrictions.

Vulnerability Detail

The vulnerability identified as CVE-2026-7737 in GoBGP arises from improper restriction of operations within the bounds of a memory buffer. This flaw can lead to potential memory corruption, allowing an attacker to exploit the system by sending specially crafted packets. The affected functions, including BMPPeerUpNotification.ParseBody and BMPStatisticsReport.ParseBody, may not adequately validate input, leading to unexpected behavior or crashes.

How To Fix

Latest published version: v4.10.0 as of 22 Oct 2026

go get github.com/osrg/gobgp/v4@v4.10.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

4.4.0

This is the first release that contains the fix.

go get github.com/osrg/gobgp/v4@v4.4.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, you can implement input validation checks in your application to ensure that any data processed by the affected functions does not exceed expected limits. However, this is not a substitute for updating to the patched version.

Conclusion

In summary, CVE-2026-7737 represents a significant vulnerability in the GoBGP package due to improper memory buffer restrictions. It is crucial for users to update to version 4.4.0 or later to mitigate the risks associated with this vulnerability. Implementing workarounds can provide temporary relief, but updating is the most effective solution.

See every vulnerability recorded for github.com/osrg/gobgp/v4 →

Share this vulnerability

FAQ

CVE-2026-7737 is a vulnerability in GoBGP that involves improper restriction of operations within the bounds of a memory buffer, potentially leading to memory corruption.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which allows you to monitor for open-source vulnerabilities without requiring any installation.

If updating is not possible, consider implementing additional input validation checks as a temporary measure to mitigate the risk of exploitation.

Exploitation of this vulnerability could lead to system crashes, unauthorized access, or other malicious activities that compromise the integrity of the BGP routing process.

More information about GoBGP, including its features and documentation, can be found on its GitHub repository at https://github.com/osrg/gobgp.

Related vulnerabilities

Recent vulnerabilities recorded for github.com/osrg/gobgp/v4.

How To Fix

Latest published version: v4.10.0 as of 22 Oct 2026

go get github.com/osrg/gobgp/v4@v4.10.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

4.4.0

This is the first release that contains the fix.

go get github.com/osrg/gobgp/v4@v4.4.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.