# CVE-2026-37460: Denial of service in n/a

> Attackers can cause a Denial of Service in FRRouting by sending a crafted BGP UPDATE message due to missing input validation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jun 2026
- **Updated:** 5 Jun 2026
- **Also known as:** ALSA-2026:49511, ALSA-2026:49527, ALSA-2026:49607, CLSA-2026-1786035720, DEBIAN-CVE-2026-37460, GHSA-4ph9-3c4q-r2hh, RHSA-2026:49511, RHSA-2026:49527, RHSA-2026:49607, RLSA-2026:49511, RLSA-2026:49527, RLSA-2026:49607, UBUNTU-CVE-2026-37460

## What is CVE-2026-37460?

CVE-2026-37460 is a high-severity denial of service vulnerability in n/a, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing input validation in the rfapiRibBi2Ri() function (rfapi_rib.c) of FRRouting (FRR) stable/10.0 to stable/10.6 allows attackers to cause a Denial of Service (DoS) via supplying a crafted BGP UPDATE message.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-37460?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `frr` | AlmaLinux:8 | All versions | 7.5.1-25.el8_10 |
| `frr-selinux` | AlmaLinux:8 | All versions | 7.5.1-25.el8_10 |
| `frr` | AlmaLinux:9 | All versions | 8.5.3-15.el9_8.1 |
| `frr-selinux` | AlmaLinux:9 | All versions | 8.5.3-15.el9_8.1 |
| `frr10` | AlmaLinux:9 | All versions | 10.4.3-3.el9_8.2 |
| `frr10-selinux` | AlmaLinux:9 | All versions | 10.4.3-3.el9_8.2 |
| `frr` | Red Hat:enterprise_linux:8::appstream | All versions | 0:7.5.1-25.el8_10 |
| `frr-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:7.5.1-25.el8_10 |
| `frr-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:7.5.1-25.el8_10 |
| `frr-selinux` | Red Hat:enterprise_linux:8::appstream | All versions | 0:7.5.1-25.el8_10 |
| `frr` | Red Hat:enterprise_linux:9::appstream | All versions | 0:8.5.3-15.el9_8.1 |
| `frr-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:8.5.3-15.el9_8.1 |
| `frr-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:8.5.3-15.el9_8.1 |
| `frr-selinux` | Red Hat:enterprise_linux:9::appstream | All versions | 0:8.5.3-15.el9_8.1 |
| `frr10` | Red Hat:enterprise_linux:9::appstream | All versions | 0:10.4.3-3.el9_8.2 |
| `frr10-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:10.4.3-3.el9_8.2 |
| `frr10-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:10.4.3-3.el9_8.2 |
| `frr10-selinux` | Red Hat:enterprise_linux:9::appstream | All versions | 0:10.4.3-3.el9_8.2 |
| `frr` | Rocky Linux:8 | All versions | 0:7.5.1-25.el8_10 |
| `frr` | Rocky Linux:9 | All versions | 0:8.5.3-15.el9_8.1 |
| `frr10` | Rocky Linux:9 | All versions | 0:10.4.3-3.el9_8.2 |

## How do I fix CVE-2026-37460?

Apply the vendor's patch.

## Is CVE-2026-37460 being exploited?

There is no known exploitation of CVE-2026-37460 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-37460 and fix it if it is affected.

What it is: CVE-2026-37460 is a high-severity denial of service vulnerability in n/a, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-37460 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-37460/ (Markdown: https://insights.sbomify.com/CVE-2026-37460/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-37460
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-37460
- OSV: https://osv.dev/vulnerability/CVE-2026-37460

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-37460/
Summaries are generated and may contain mistakes; the official description above is the record.