CVE-2026-7737
Out-of-Bounds Read in GoBGP BMP Parser
Publication date: 2026-05-04
Last updated on: 2026-05-06
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| osrg | gobgp | to 4.4.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the osrg GoBGP software up to version 4.3.0, specifically in the BMP Parser component's functions BMPPeerUpNotification.ParseBody and BMPStatisticsReport.ParseBody. These functions previously read fixed-size fields from input data without verifying that the input was long enough, which could lead to out-of-bounds memory reads. This means that if an attacker sends malformed input data, the program might access memory outside the intended bounds, potentially causing crashes or other unintended behavior.
The issue is fixed in version 4.4.0 by adding input length validation before reading the data, ensuring that the functions return an error if the input is too short instead of causing a crash.
How can this vulnerability impact me? :
This vulnerability can be exploited remotely by sending specially crafted malformed input to the affected BMP Parser functions. The impact is an out-of-bounds read, which can cause the application to crash or behave unpredictably. Such crashes can lead to denial of service conditions, potentially disrupting network routing operations managed by GoBGP.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves out-of-bounds reads in the BMP packet parsing functions of GoBGP. Detection would involve monitoring for malformed BMP packets that could trigger these parsing errors.
Since the issue arises from insufficient input length validation in BMPStatisticsReport.ParseBody and BMPPeerUpNotification.ParseBody, one way to detect exploitation attempts is to capture and analyze BMP traffic for packets with abnormally short or malformed payloads.
No specific detection commands are provided in the available information.
What immediate steps should I take to mitigate this vulnerability?
The recommended immediate mitigation step is to upgrade the affected GoBGP component to version 4.4.0 or later, where the vulnerability has been fixed.
The fix involves adding input length validation in the BMP packet parsing code to prevent out-of-bounds reads and crashes.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not include any details on how the vulnerability in GoBGP affects compliance with common standards and regulations such as GDPR or HIPAA.