# CVE-2026-24470: Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName

> Attackers with Ingress creation permissions can access internal services via ExternalName, bypassing network restrictions.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jan 2026
- **Updated:** 27 Jan 2026
- **Also known as:** GHSA-mxxc-p822-2hx9, GO-2026-4378

## What is CVE-2026-24470?

CVE-2026-24470 is a high-severity server-side request forgery vulnerability in zalando skipper, published on 26 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-441 (Unintended Proxy or Intermediary)

## Which versions are affected by CVE-2026-24470?

3 open source packages ship an affected version, including github.com/zalando/skipper. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/zalando/skipper` | Go | All versions | 0.24.0 |
| `github.com/zalando/skipper` | Go | All versions | 0.24.0 |
| `github.com/zalando/skipper` | Go | All versions | 0.24.0 |

Products: Zalando Skipper.

## How do I fix CVE-2026-24470?

Upgrade github.com/zalando/skipper to 0.24.0 or later.

## Is CVE-2026-24470 being exploited?

There is no known exploitation of CVE-2026-24470 in the wild and no public exploit code.

## Other vulnerabilities in zalando skipper

- [CVE-2022-38580](https://insights.sbomify.com/CVE-2022-38580/): Skipper vulnerable to SSRF via X-Skipper-Proxy (critical 9.8)
- [CVE-2026-23742](https://insights.sbomify.com/CVE-2026-23742/): Skipper arbitrary code execution through lua filters (high 8.8)
- [CVE-2022-34296](https://insights.sbomify.com/CVE-2022-34296/): Query predicate bypass in Zalando Skipper (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24470 and fix it if it is affected.

What it is: CVE-2026-24470 is a high-severity server-side request forgery vulnerability in zalando skipper, published on 26 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24470 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/zalando/skipper (Go): affected all versions; fixed in 0.24.0
- github.com/zalando/skipper (Go): affected all versions; fixed in 0.24.0
- github.com/zalando/skipper (Go): affected all versions; fixed in 0.24.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24470/ (Markdown: https://insights.sbomify.com/CVE-2026-24470/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24470
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24470
- OSV: https://osv.dev/vulnerability/CVE-2026-24470

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24470/
Summaries are generated and may contain mistakes; the official description above is the record.