Calico's Application Layer Policy (disabled by default), which enforces HTTP rules through Dikastes, fails to perform URL path normalization. As a result, HTTP requests using path-traversal segments, encoded slashes, or repeated slashes are not correctly evaluated by Prefix path rules. Dikastes authorizes the request under the permitted prefix while the downstream workload or a fronting proxy normalizes the path and serves the restricted endpoint. An attacker with network access and no special RBAC can potentially reach HTTP endpoints the policy was intended to restrict.
References
| Link | Resource |
|---|---|
| https://github.com/projectcalico/calico/pull/12531 | Issue Tracking Patch |
| https://github.com/projectcalico/calico/pull/12532 | Issue Tracking Patch |
| https://github.com/projectcalico/calico/pull/12533 | Issue Tracking Patch |
| https://www.tigera.io/security-bulletins/tta-2026-005/ | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-07-30 15:16
Updated : 2026-08-08 01:10
NVD link : CVE-2026-6540
Mitre link : CVE-2026-6540
CVE.ORG link : CVE-2026-6540
JSON object : View
Products Affected
tigera
- calico
