CVE-2026-7736: A vulnerability was determined in osrg GoBGP up to 4.3.0

Q: How do I fix CVE-2026-7736?

gobgp: upgrade to 4.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-7736 being exploited?

CVE-2026-7736 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-7736 affect?

CVE-2026-7736 affects gobgp. Severity is high (CVSS 7.3). 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 a

Q: How urgent is CVE-2026-7736?

Priority 40/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.3REMOTEUPGRADE

CVE-2026-7736 is a high-severity flaw (CVSS 7.3) affecting gobgp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 61%)
CISA exploited list	No
Weakness	CWE-189, CWE-191
Published	2026-05-04
Last modified	2026-10-26

Publisher (CNA): VulDB · Vendor: osrg

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-04 07:16 UTCPublished CVE record published
2026-10-26 19:10 UTCUpdated Record last modified

osrg gobgp UPGRADE

Affected: < 4.4.0

Fixed in: 4.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy gobgp || rpm -q gobgp || gobgp --version

2. UPGRADE to 4.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gobgp

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gobgp

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-7736?

gobgp: upgrade to 4.4.0. Exact commands for each OS are on this page.

Is CVE-2026-7736 being exploited?

CVE-2026-7736 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-7736 affect?

CVE-2026-7736 affects gobgp. Severity is high (CVSS 7.3). 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 a

How urgent is CVE-2026-7736?

Priority 40/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-7735 HIGH 7.3 UPGRADE A vulnerability was found in osrg GoBGP up to 4.3.0
CVE-2026-7737 MEDIUM 5.3 UPGRADE A vulnerability was identified in osrg GoBGP up to 4.3.0
CVE-2026-7734 MEDIUM 5.3 UPGRADE A vulnerability has been found in osrg GoBGP up to 4.3.0

References

← Back to latest CVEs