Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName
GHSA-mxxc-p822-2hx9 · CVE-2026-24470 · GO-2026-4378
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
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
References
- WEB https://github.com/zalando/skipper/security/advisories/GHSA-mxxc-p822-2hx9
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-24470
- WEB https://github.com/zalando/skipper/commit/a4c87ce029a58eb8e1c2c1f93049194a39cf6219
- PACKAGE https://github.com/zalando/skipper
- WEB https://github.com/zalando/skipper/releases/tag/v0.24.0
- WEB https://kubernetes.io/docs/concepts/services-networking/service/#externalname
Ready to move
Start Securing
Free, no credit card | First findings in minutes