Skip to main content
VulnerabilityPublished Updated

CVE-2023-38407: frr

Affects frrSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 8.5 soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade frrouting/frr to 8.5.

Affected software

ProductAffectedFixed in
GitHubfrrouting/frrpkg:github/frrouting/frrOther threatsAffected
  • <8.5
Fixed in
  • 8.5

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

AI-suggested

The most effective mitigation is to upgrade FRRouting to version 8.5 or later, where this vulnerability has been addressed. Until patching is possible, network administrators should implement strict filtering of incoming BGP labeled unicast messages from untrusted sources to reduce exposure. Monitoring the stability and logs of the bgpd daemon can help detect attempts to exploit this vulnerability. Employing network segmentation and limiting BGP peering to trusted partners reduces the attack surface. Additionally, organizations should maintain up-to-date backups of router configurations and have incident response plans ready to quickly recover from potential outages. Coordinating with upstream providers and peers to ensure they are also patched can help prevent exploitation through external BGP sessions.

Description

bgpd/bgp_label.c in FRRouting (FRR) before 8.5 attempts to read beyond the end of the stream during labeled unicast parsing.

References

Community reviews

Loading reviews…