CVE-2026-24470: Skipper is an HTTP router and reverse proxy for service composition

Q: How do I fix CVE-2026-24470?

skipper: upgrade to 0.24.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-24470 being exploited?

CVE-2026-24470 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-24470 affect?

CVE-2026-24470 affects skipper. Severity is high (CVSS 8.1). 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 th

Routine

HIGH 8.1UPGRADE

CVE-2026-24470 is a high-severity flaw (CVSS 8.1) affecting skipper. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 a

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-441, CWE-918
Published	2026-01-26
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: zalando

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-01-26 23:16 UTCPublished CVE record published
2026-06-17 10:23 UTCUpdated Record last modified

zalando skipper UPGRADE

Affected: < 0.24.0

Fixed in: 0.24.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy skipper || rpm -q skipper || skipper --version

2. UPGRADE to 0.24.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade skipper

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade skipper

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-24470?

skipper: upgrade to 0.24.0. Exact commands for each OS are on this page.

Is CVE-2026-24470 being exploited?

CVE-2026-24470 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-24470 affect?

CVE-2026-24470 affects skipper. Severity is high (CVSS 8.1). 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 th

How urgent is CVE-2026-24470?

Priority 34/100. High severity

Software pages

Kubernetes vulnerabilities

Related CVEs

CVE-2026-23742 HIGH 8.8 UPGRADE Skipper is an HTTP router and reverse proxy for service composition

References

← Back to latest CVEs