# CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation

Advisory record · `GHSA-q6h5-q3q6-f87x`

- **Identifiers:** `GHSA-q6h5-q3q6-f87x` · `BIT-cilium-2026-53935` · `BIT-cilium-operator-2026-53935` · `BIT-hubble-relay-2026-53935` · `CVE-2026-53935` · `GO-2026-5914`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-601](https://cwe.mitre.org/data/definitions/601.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Open redirect](https://agentprime.io/advisories/tag/open-redirect.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 6 Jul 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 Jul 2026, 20:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/cilium/cilium` (Go): affected `>=1.19.0, <1.19.4 || >=1.18.2, <1.18.10 || <1.17.16`; fixed in `1.19.4`, `1.18.10`, `1.17.16`

## Machine-written summary

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

> Cilium (github.com/cilium/cilium) versions before 1.17.16, from 1.18.2 before 1.18.10, and from 1.19.0 before 1.19.4 are affected. A user who can create CiliumLocalRedirectPolicies can use the addressMatcher field to specify arbitrary ClusterIPs, redirecting traffic meant for Services in any namespace, and deleting such a policy can break service translation for the affected Service. Upgrade to 1.17.16, 1.18.10, or 1.19.4. The source lists no workaround.

Written 1 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

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

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

## Timeline

- 31 Oct 2026, 14:13 UTC: First seen by agentprime
- 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-q6h5-q3q6-f87x)

## Sources

- [GitHub Advisory Database: GHSA-q6h5-q3q6-f87x](https://github.com/advisories/GHSA-q6h5-q3q6-f87x)
- [OSV: GHSA-q6h5-q3q6-f87x](https://osv.dev/vulnerability/GHSA-q6h5-q3q6-f87x)
- <https://github.com/cilium/cilium/security/advisories/GHSA-q6h5-q3q6-f87x>
- <https://github.com/cilium/cilium/pull/44512>
- <https://github.com/cilium/cilium/pull/44584>
- <https://github.com/cilium/cilium/pull/44585>
- <https://github.com/cilium/cilium>

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-q6h5-q3q6-f87x>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-q6h5-q3q6-f87x/>. Everything for agents: <https://agentprime.io/llms.txt>.
