How severe is CVE-2026-7736?

No CVSS score has been assigned to CVE-2026-7736 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-7736?

CVE-2026-7736 affects the following packages: github.com/osrg/gobgp/v4 (Go). Ecosystems affected: Go.

How do I fix CVE-2026-7736?

Update github.com/osrg/gobgp/v4 to 4.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-7736 is resolved across your whole dependency graph.

How do I detect CVE-2026-7736 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/osrg/gobgp/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-7736 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-7736 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-7736 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-7736?

CVE-2026-7736 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-7736?

CVE-2026-7736 is classified as CWE-189 (CWE-189), CWE-191 (CWE-191). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-7736 published, and has it been updated?

CVE-2026-7736 was published on May 4, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2026-7736 — gobgp

Fix: osrg/gobgp@76d9110

CVE-2026-7736 is a CWE-189 vulnerability in github.com/osrg/gobgp/v4. A fix is available for github.com/osrg/gobgp/v4 — see the affected versions and patch details below.

osrg GoBGP mrt.go parseRibEntry integer underflow

Also known asGHSA-hj4w-qr9j-c4cfGO-2026-5427

Published

May 4, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-7736.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/osrg/gobgp/v4

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/osrg/gobgp/v4`	all versions	4.4.0`go get github.com/osrg/gobgp/v4@v4.4.0`

Affected Products

1 product · 1 configurations

Application

gobgposrg

< 4.4.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/osrg/gobgp/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/osrg/gobgp/v4 to 4.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-7736 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

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…

Workaround published by Red Hat

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.

Source: Red Hat security advisory for CVE-2026-7736 (CC BY 4.0)

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-7736 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works