CVE-2026-53935 json
CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation
published 4mo ago modified 2mo ago also BIT-cilium-2026-53935 , BIT-cilium-operator-2026-53935 , BIT-hubble-relay-2026-53935 , EUVD-2026-42101 , GHSA-q6h5-q3q6-f87x , GO-2026-5914
- cvss
- 6.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
Cilium is a networking, observability, and security solution. Prior to 1.17.16, from 1.18.2 to 1.18.9, and from 1.19.0 to 1.19.3, users with the ability to create CiliumLocalRedirectPolicies can specify arbitrary ClusterIPs via addressMatcher, enabling hijacking traffic to Services in any namespace and bypassing namespace scoping enforced by serviceMatcher; deleting such a policy can also corrupt Cilium internal service state and stop service translation for the affected Service. This issue is fixed in versions 1.17.16, 1.18.10, and 1.19.4.
Patch / fix
- go github.com/cilium/cilium 1.17.16, 1.18.10, 1.19.4
- bitnami cilium 1.17.16, 1.18.10, 1.19.4
- bitnami cilium-operator 1.17.16, 1.18.10, 1.19.4
- bitnami hubble-relay 1.17.16, 1.18.10, 1.19.4
- cilium cilium 1.17.16, 1.18.10, 1.19.4
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
- github.com/cilium/cilium@81d4463 commit
- github.com/cilium/cilium@92ca32e commit
- github.com/cilium/cilium@fe7eb53 commit
- github.com/cilium/cilium#45412 pull request
- github.com/cilium/cilium#45584 pull request
- github.com/cilium/cilium#45585 pull request
- github.com/cilium/cilium#44512 pull request
- github.com/cilium/cilium#44584 pull request
- github.com/cilium/cilium#44585 pull request
Is CVE-2026-53935 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.9 | CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:H |
| GitHub | 3.1 | 6.9 | CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:H |
| OSV | 3.1 | 6.9 | CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/cilium/cilium | >=1.19.0, <1.19.4 >=1.18.2, <1.18.10 <1.17.16 |
1.19.4 1.18.10 1.17.16 |
| bitnami | cilium | <1.17.16 >=1.18.2, <1.18.10 >=1.19.0, <1.19.4 |
1.17.16 1.18.10 1.19.4 |
| bitnami | cilium-operator | <1.17.16 >=1.18.2, <1.18.10 >=1.19.0, <1.19.4 |
1.17.16 1.18.10 1.19.4 |
| bitnami | hubble-relay | <1.17.16 >=1.18.2, <1.18.10 >=1.19.0, <1.19.4 |
1.17.16 1.18.10 1.19.4 |
Affected products
- cilium cilium
Classification
References
-
github.com
/cilium/cilium/pull/45412
web
-
github.com
/cilium/cilium/pull/45584
web
-
github.com
/cilium/cilium/pull/45585
web
-
github.com
/cilium/cilium/commit/81d446395673dc2c684c047c12715caffac1a351
web
-
github.com
/cilium/cilium/commit/92ca32eda85aa0c7611c28221cc26fa08be17ebc
web
-
github.com
/cilium/cilium/commit/fe7eb53c7aac9fa7ec610b1975d73fbbb198c66d
web
-
github.com
/cilium/cilium/pull/44512
web, patch
-
github.com
/cilium/cilium/pull/44584
web, patch
-
github.com
/cilium/cilium/pull/44585
web, patch
-
github.com
/cilium/cilium/security/advisories/GHSA-q6h5-q3q6-f87x
web, advisory
-
github.com
/cilium/cilium
package
-
nvd.nist.gov
/vuln/detail/CVE-2026-53935
web
Sources
- CVE List CVE-2026-53935
- GitHub Advisory GHSA-q6h5-q3q6-f87x
- NVD CVE-2026-53935
- OSV BIT-cilium-2026-53935
- OSV BIT-cilium-operator-2026-53935
- OSV BIT-hubble-relay-2026-53935
- OSV GO-2026-5914
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.