Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-mxxc-p822-2hx9 | Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName |
Wed, 18 Feb 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:zalando:skipper:*:*:*:*:*:*:*:* |
Tue, 27 Jan 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 27 Jan 2026 09:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Zalando
Zalando skipper |
|
| Vendors & Products |
Zalando
Zalando skipper |
Mon, 26 Jan 2026 22:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName | |
| Weaknesses | CWE-441 CWE-918 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-01-27T14:51:35.229Z
Reserved: 2026-01-23T00:38:20.546Z
Link: CVE-2026-24470
Updated: 2026-01-27T14:51:31.267Z
Status : Analyzed
Published: 2026-01-26T23:16:09.123
Modified: 2026-02-18T17:39:44.020
Link: CVE-2026-24470
No data.
OpenCVE Enrichment
Updated: 2026-04-18T15:00:03Z
Github GHSA