Skip to main content
VulnerabilityPublished

CVE-2026-5122: osrg GoBGP · Improper Access Controls

Affects osrg GoBGPSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
osrgGoBGPAffected
  • 4.0 – 4.3.0
4 affected builds
Fixed in–
Gogithub.com/osrg/gobgppkg:golang/github.com/osrg/gobgpOther threatsAffected
  • 4.0 – 4.3.0
4 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patch identified by commit 2b09db390a3d455808363c53e409afe6b1b86d2d immediately to all affected GoBGP instances (versions 4.0 through 4.3.0). In addition, network administrators should: 1) Restrict BGP session establishment to trusted peers only, using access control lists and firewall rules to limit exposure. 2) Monitor BGP session logs for unusual OPEN message activity or anomalies in domainNameLen values. 3) Employ network segmentation to isolate BGP routers from untrusted networks. 4) Use BGP session authentication mechanisms such as TCP MD5 signatures or TCP-AO to reduce risk of unauthorized session manipulation. 5) Regularly update and audit GoBGP deployments to ensure no outdated versions remain. 6) Implement anomaly detection systems focused on BGP traffic to identify potential exploitation attempts early.

Description

A security flaw has been discovered in osrg GoBGP up to 4.3.0. This affects the function DecodeFromBytes of the file pkg/packet/bgp/bgp.go of the component BGP OPEN Message Handler. Performing a manipulation of the argument domainNameLen results in improper access controls. The attack may be initiated remotely. A high degree of complexity is needed for the attack. The exploitability is reported as difficult. The patch is named 2b09db390a3d455808363c53e409afe6b1b86d2d. It is suggested to install a patch to address this issue.

References

Community reviews

Loading reviews…