Github.Com Zalando Skipper vulnerabilities

CVE-2022-38580 [CRITICAL] CWE-918 Skipper vulnerable to SSRF via X-Skipper-Proxy Skipper vulnerable to SSRF via X-Skipper-Proxy ### Impact Skipper prior to version v0.13.236 is vulnerable to server-side request forgery (SSRF). An attacker can exploit a vulnerable version of proxy to access the internal metadata server or other unauthenticated URLs by adding an specific header (X-Skipper-Proxy) to the http request. ### Patches The problem was patched in version https://github.com/zalando/skipp

CVE-2026-23742 [HIGH] CWE-250 Skipper is vulnerable to arbitrary code execution through lua filters Skipper is vulnerable to arbitrary code execution through lua filters ### Impact Arbitrary code execution through [lua filters](https://opensource.zalando.com/skipper/reference/scripts/). The default skipper configuration before v0.23 was `-lua-sources=inline,file`. The problem starts if untrusted users can create lua filters, because of `-lua-sources=inline` , for example through a Kubernetes

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/rel

CVE-2022-34296 [HIGH] Query predicate bypass in Zalando Skipper Query predicate bypass in Zalando Skipper In Zalando Skipper before 0.13.218, a query predicate could be bypassed via a prepared request.