# CVE-2026-5107: FRRouting FRR EVPN Type-2 Route bgp_evpn.c process_type2_route access control

> Remote attackers can bypass access controls in the EVPN Type-2 Route handler, requiring high complexity and difficult exploitation.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** AZL-81087, DEBIAN-CVE-2026-5107, GHSA-27p7-fq6v-hh4m, UBUNTU-CVE-2026-5107, openSUSE-SU-2026:10606-1

## What is CVE-2026-5107?

CVE-2026-5107 is a low-severity missing authorization vulnerability in FRRouting FRR, published on 30 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in FRRouting FRR up to 10.5.1. This affects the function process_type2_route of the file bgpd/bgp_evpn.c of the component EVPN Type-2 Route Handler. The manipulation leads to improper access controls. The attack can be initiated remotely. The attack is considered to have high complexity. The exploitability is reported as difficult. The identifier of the patch is 7676cad65114aa23adde583d91d9d29e2debd045. To fix this issue, it is recommended to deploy a patch.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `frr` | openSUSE:Tumbleweed | All versions | 10.5.1-3.1 |

Products: Frrouting Frrouting.

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

Apply the vendor's patch.

## Is CVE-2026-5107 being exploited?

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

## Other vulnerabilities in FRRouting FRR

- [CVE-2024-44070](https://insights.sbomify.com/CVE-2024-44070/): Denial of service in n/a (critical 9.8)
- [CVE-2023-38406](https://insights.sbomify.com/CVE-2023-38406/): bgpd/bgp_flowspec.c in FRRouting (FRR) before 8.4.3 mishandles an nlri length of zero, aka a "flowspec overflow." (critical 9.8)
- [CVE-2022-37035](https://insights.sbomify.com/CVE-2022-37035/): Use after free in n/a (high 8.1)
- [CVE-2022-26127](https://insights.sbomify.com/CVE-2022-26127/): Memory corruption in FRRouting (high 7.8)
- [CVE-2022-26128](https://insights.sbomify.com/CVE-2022-26128/): Memory corruption in FRRouting (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5107 is a low-severity missing authorization vulnerability in FRRouting FRR, published on 30 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5107 in the wild and no public exploit code.

Affected product: FRRouting FRR. 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-5107/ (Markdown: https://insights.sbomify.com/CVE-2026-5107/index.md)
```

## Sources

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

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