cve.bz

CVE-2026-7736 osrg gobgp: Numeric Errors

6.9 mediumEPSS 0.5%Fix available

Medium (6.9) in osrg gobgp. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/osrg/gobgp/v4 4.4.0.

On this page
A vulnerability was determined in osrg GoBGP up to 4.3.0. Affected by this vulnerability is the function parseRibEntry of the file pkg/packet/mrt/mrt.go. Executing a manipulation can lead to integer underflow. It is possible to launch the attack remotely. Upgrading to version 4.4.0 addresses this issue. This patch is called 76d911046344a3923cbe573364197aa081944592. It is suggested to upgrade the affected component.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-05-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-189 Numeric Errors
CWE-191 Integer Underflow (Wrap or Wraparound)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-7736 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-7736?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-7736?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-7736 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-7736

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-7736](https://cve.bz/cve/badge/CVE-2026-7736.svg)](https://cve.bz/cve/CVE-2026-7736)

HTML:

<a href="https://cve.bz/cve/CVE-2026-7736"><img src="https://cve.bz/cve/badge/CVE-2026-7736.svg" alt="CVE-2026-7736"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
osrg:gobgpbefore 4.4.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-hj4w-qr9j-c4cfGogithub.com/osrg/gobgp/v4<4.4.04.4.0
GO-2026-5427Gogithub.com/osrg/gobgp/v4<4.4.04.4.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13gobgpno fix listedDEBIAN-CVE-2026-7736
Debian14gobgp4.4.0-1DEBIAN-CVE-2026-7736
Ubuntu25.10gobgpno fix listedUBUNTU-CVE-2026-7736
UbuntuPro:18.04:LTSgobgp1.29-1ubuntu0.1+esm2UBUNTU-CVE-2026-7736 USN-8348-1
UbuntuPro:20.04:LTSgobgp2.12.0-1ubuntu0.1~esm3UBUNTU-CVE-2026-7736 USN-8348-1
UbuntuPro:22.04:LTSgobgp2.25.0-3ubuntu0.1+esm4UBUNTU-CVE-2026-7736 USN-8348-1
UbuntuPro:24.04:LTSgobgp3.23.0-1ubuntu0.3+esm4UBUNTU-CVE-2026-7736 USN-8348-1
UbuntuPro:26.04:LTSgobgp3.36.0-2ubuntu0.1~esm1UBUNTU-CVE-2026-7736 USN-8348-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This flaw is rated as Important. A remote unauthenticated attacker whose is able to reach the application consuming the GoBGP library to handle `MRT` information can trigger the integer underflow vulnerability by sending a maliciously crafted packet to the application. The value resulted from the underflow is further used to try to read information from the memory buffer holding the packet itself resulting in a out-of-bounds read. As the Go language is considered memory safe, in this implementation the attacker won't be able to read any unintended data as the Go runtime will case the application to panic meaning there's no integrity or confidentiality impact as consequence of a successful attacker. However when this flaw is exploited, due to the same runtime protection leading the application to panic, a denial-of-service (DoS) is achieved for all users trying to access the application, result in a high impact to the availability aspect.

Red Hat's mitigation

To mitigate this issue, restrict network access to systems running GoBGP to only trusted BGP peers. Configure firewall rules to limit inbound connections to the BGP port (TCP 179) from known and authorized sources. This will reduce the attack surface by preventing arbitrary remote attackers from sending malicious BGP messages. Any changes to firewall rules or network configurations may require a service reload or restart to take effect, which could temporarily disrupt network services.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-7736.

References

Check your stackJSON