What’s Vulnerable › Vulnerabilities
CVE-2026-24470: Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName
- Severity: high (CVSS 8.1 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.3% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-01-26 · updated 2026-06-17
- Weakness: CWE-441
Description
Skipper is an HTTP router and reverse proxy for service composition. Prior to version 0.24.0, when running Skipper as an Ingress controller, users with permissions to create an Ingress and a Service of type ExternalName can create routes that enable them to use Skipper's network access to reach internal services. Version 0.24.0 disables Kubernetes ExternalName by default. As a workaround, developers can allow list targets of an ExternalName and allow list via regular expressions.
Affected products
- zalando skipper: before 0.24.0 — fixed in 0.24.0
How to fix
Upgrade to a fixed version: zalando skipper 0.24.0. Check the vendor advisory for mitigations.
References
- https://github.com/zalando/skipper/commit/a4c87ce029a58eb8e1c2c1f93049194a39cf6219
- https://github.com/zalando/skipper/security/advisories/GHSA-mxxc-p822-2hx9
- https://kubernetes.io/docs/concepts/services-networking/service/#externalname
Get alerted when CVE-2026-24470 or the next vulnerability affects your stack