CVE-2023-46753: frr · Incorrect Authorization
Affects frrSource CVE Database V5
Not known to be exploited.
Data as of 26 Oct 2026, 14:05 UTC
Rated Medium by the CNA (mitre) · No CVSS score from NVD or the CNA
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 26 Oct 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfrrouting/frrpkg:github/frrouting/frrOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Since the affected versions are up to 9.0.1, users should monitor vendor advisories for updates or patches addressing this issue. Until a fix is available, cautious handling of BGP UPDATE messages and network-level filtering of suspicious BGP traffic may help reduce exposure.
Description
FRRouting (FRR) versions up to and including 9.0.1 contain a vulnerability where processing a crafted BGP UPDATE message lacking mandatory attributes can cause the software to crash. This occurs, for example, when the message includes only an unknown transit attribute.