# Kube-router Proxy Module Blindly Trusts ExternalIPs/LoadBalancer IPs Enabling Cluster-Wide Traffic Hijacking and DNS DoS

Advisory record · `GHSA-phqm-jgc3-qf8g`

- **Identifiers:** `GHSA-phqm-jgc3-qf8g` · `CVE-2026-32254` · `GO-2026-4724`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 17 Mar 2026
- **Updated:** 30 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 Mar 2026, 17:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/cloudnativelabs/kube-router/v2` (Go): affected `<2.8.0`; fixed in `2.8.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> kube-router versions before 2.8.0 have a flaw in the proxy module, which copies Service externalIPs and LoadBalancer IPs onto cluster nodes without checking them against the configured --service-external-ip-range. An attacker who holds namespace-scoped permission to create or modify Services can bind arbitrary IPs on all nodes and redirect traffic, including cluster DNS, to their own pods. Upgrade to kube-router 2.8.0 or later. The source gives few details on workarounds.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0034, the 28th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:08 UTC: First seen by agentprime
- 31 Oct 2026, 15:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-phqm-jgc3-qf8g)

## Sources

- [GitHub Advisory Database: GHSA-phqm-jgc3-qf8g](https://github.com/advisories/GHSA-phqm-jgc3-qf8g)
- [OSV: GHSA-phqm-jgc3-qf8g](https://osv.dev/vulnerability/GHSA-phqm-jgc3-qf8g)
- <https://github.com/cloudnativelabs/kube-router/security/advisories/GHSA-phqm-jgc3-qf8g>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-32254>
- <https://github.com/cloudnativelabs/kube-router/commit/a1f0b2eea3ee0f66b9a5b5c49dcb714619ccd456>
- <https://github.com/cloudnativelabs/kube-router>
- <https://github.com/cloudnativelabs/kube-router/releases/tag/v2.8.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-phqm-jgc3-qf8g>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-phqm-jgc3-qf8g/>. Everything for agents: <https://agentprime.io/llms.txt>.
