CVE-2026-24470
published 2026-01-26CVE-2026-24470: 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…
PriorityP350high8.1CVSS 3.1
AVNACLPRLUINSUCHIHAN
EPSS
0.27%
18.2th percentile
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
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| github.com | zalando_skipper | >= 0 < 0.24.0 | 0.24.0 |
| zalando | skipper | < 0.24.0 | 0.24.0 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName in github.com/zalando/skipper
osv·2026-02-02
CVE-2026-24470 Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName in github.com/zalando/skipper
Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName in github.com/zalando/skipper
Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName in github.com/zalando/skipper
OSV
Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName
osv·2026-01-26
CVE-2026-24470 [HIGH] Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName
Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName
### Impact
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.
### Patches
https://github.com/zalando/skipper/releases/tag/v0.24.0 disables Kubernetes ExternalName by default.
### Workarounds
Developers can allow list targets of an ExternalName by using `-kubernetes-only-allowed-external-names=true` and allow list via regular expressions `-kubernetes-allowed-external-name '^[a-z][a-z0-9-.]+[.].allowed.example$'`
### References
https://kubernetes.io/docs/concepts/services-networking/service/#externalname
GHSA
Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName
ghsa·2026-01-26
CVE-2026-24470 [HIGH] CWE-441 Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName
Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName
### Impact
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.
### Patches
https://github.com/zalando/skipper/releases/tag/v0.24.0 disables Kubernetes ExternalName by default.
### Workarounds
Developers can allow list targets of an ExternalName by using `-kubernetes-only-allowed-external-names=true` and allow list via regular expressions `-kubernetes-allowed-external-name '^[a-z][a-z0-9-.]+[.].allowed.example$'`
### References
https://kubernetes.io/docs/concepts/services-networking/service/#externalname
No detection rules found.
No public exploits indexed.
2026-01-26
Published