Improper Access Control Affecting hubble-ui package, versions <0.13.4-r3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Improper Access Control vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-WOLFILATEST-HUBBLEUI-15855108
- published31 Mar 2026
- disclosed27 Mar 2026
Introduced: 27 Mar 2026
NewCVE-2026-33726 (opens in a new tab)How to fix?
Upgrade Wolfi hubble-ui to version 0.13.4-r3 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream hubble-ui package and not the hubble-ui package as distributed by Wolfi.
See How to fix? for Wolfi relevant fixed versions and status.
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.17.14, 1.18.8, and 1.19.2, Ingress Network Policies are not enforced for traffic from pods to L7 Services (Envoy, GAMMA) with a local backend on the same node, when Per-Endpoint Routing is enabled and BPF Host Routing is disabled. Per-Endpoint Routing is disabled by default, but is automatically enabled in deployments using cloud IPAM, including Cilium ENI on EKS (eni.enabled), AlibabaCloud ENI (alibabacloud.enabled), Azure IPAM (azure.enabled, but not AKS BYOCNI), and some GKE deployments (gke.enabled; managed offerings such as GKE Dataplane V2 may use different defaults). It is typically not enabled in tunneled deployments, and chaining deployments are not affected. In practice, Amazon EKS with Cilium ENI mode is likely the most common affected environment. Versions 1.17.14, 1.18.8, and 1.19.2 contain a patch. There is currently no officially verified or comprehensive workaround for this issue. The only option would be to disable per-endpoint routes, but this will likely cause disruptions to ongoing connections, and potential conflicts if running in cloud providers.
References
- https://docs.cilium.io/en/stable/network/concepts/routing/#routing
- https://docs.cilium.io/en/stable/network/kubernetes/policy/#network-policy
- https://docs.cilium.io/en/stable/network/servicemesh/l7-traffic-management
- https://docs.cilium.io/en/stable/operations/performance/tuning/#ebpf-host-routing
- https://github.com/cilium/cilium/pull/44693
- https://github.com/cilium/cilium/security/advisories/GHSA-hxv8-4j4r-cqgv