Search
Search Results (4 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-24470 | 1 Zalando | 1 Skipper | 2026-01-27 | 8.1 High |
| 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. | ||||
| CVE-2026-23742 | 1 Zalando | 1 Skipper | 2026-01-26 | 8.8 High |
| Skipper is an HTTP router and reverse proxy for service composition. The default skipper configuration before 0.23.0 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 Ingress resource. The configuration inline allows these user to create a script that is able to read the filesystem accessible to the skipper process and if the user has access to read the logs, they an read skipper secrets. This vulnerability is fixed in 0.23.0. | ||||
| CVE-2022-38580 | 1 Zalando | 1 Skipper | 2025-05-07 | 9.8 Critical |
| Zalando Skipper v0.13.236 is vulnerable to Server-Side Request Forgery (SSRF). | ||||
| CVE-2022-34296 | 1 Zalando | 1 Skipper | 2024-11-21 | 7.5 High |
| In Zalando Skipper before 0.13.218, a query predicate could be bypassed via a prepared request. | ||||
Page 1 of 1.