Cilium up to 1.17.15/1.18.9/1.19.3 CiliumLocalRedirectPolicy addressMatcher redirect
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.57+ |
Summary
A vulnerability has been found in Cilium up to 1.17.15/1.18.9/1.19.3 and classified as problematic. The affected element is an unknown function of the component CiliumLocalRedirectPolicy. Performing a manipulation of the argument addressMatcher results in redirect. This vulnerability is identified as CVE-2026-53935. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in Cilium up to 1.17.15/1.18.9/1.19.3. It has been classified as problematic. This affects an unknown part of the component CiliumLocalRedirectPolicy. The manipulation of the argument addressMatcher with an unknown input leads to a redirect vulnerability. CWE is classifying the issue as CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. This is going to have an impact on integrity. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-53935 since 06/11/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1204.001 for this issue.
Upgrading to version 1.17.16, 1.18.10 or 1.19.4 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 1.17.0
- 1.17.1
- 1.17.2
- 1.17.3
- 1.17.4
- 1.17.5
- 1.17.6
- 1.17.7
- 1.17.8
- 1.17.9
- 1.17.10
- 1.17.11
- 1.17.12
- 1.17.13
- 1.17.14
- 1.17.15
- 1.18.0
- 1.18.1
- 1.18.2
- 1.18.3
- 1.18.4
- 1.18.5
- 1.18.6
- 1.18.7
- 1.18.8
- 1.18.9
- 1.19.0
- 1.19.1
- 1.19.2
- 1.19.3
Website
- Product: https://github.com/cilium/cilium/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: RedirectCWE: CWE-601
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: Cilium 1.17.16/1.18.10/1.19.4
Timeline
06/11/2026 CVE reserved07/07/2026 Advisory disclosed
07/07/2026 VulDB entry created
07/07/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-53935 (🔒)
GCVE (CVE): GCVE-0-2026-53935
GCVE (VulDB): GCVE-100-376701
Entry
Created: 07/07/2026 23:37Changes: 07/07/2026 23:37 (53)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.