LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24470 affects Zalando Skipper used as a Kubernetes Ingress controller. A Kubernetes user who can create both Ingress objects and ExternalName Services may route traffic through Skipper to internal services they should not reach. This can expose or allow modification of sensitive internal systems, depending on reachable services.

Executive priority

Prioritize remediation for shared Kubernetes clusters or environments with delegated namespace administration. This issue can turn ordinary configuration rights into unauthorized internal service access. Treat as high priority where Skipper can reach sensitive internal systems.

Technical view

Before Skipper 0.24.0, ExternalName Services were allowed by default in Ingress routing. With low Kubernetes privileges, an attacker could define an Ingress and ExternalName Service causing Skipper to act as a proxy to internal targets. The CVSS score is 8.1, with high confidentiality and integrity impact and no user interaction required.

Likely exposure

Exposure is likely limited to Kubernetes clusters running Skipper as an Ingress controller before version 0.24.0, where users or workloads can create Ingress resources and ExternalName Services. Clusters with strict RBAC preventing those combined permissions have reduced exposure.

Exploitation context

The sources describe a privilege-abuse path using legitimate Kubernetes objects, not a remote unauthenticated takeover. No cited source or KEV listing indicates active exploitation. The main risk is lateral access through Skipper’s network position into internal services.

Researcher notes

The advisory maps to CWE-441 and CWE-918, reflecting confused-deputy and server-side request forgery style behavior. The key control boundary is Skipper’s network reach versus Kubernetes users’ object creation rights. Evidence is sufficient for affected versions and vendor mitigation, but public sources do not show exploitation in the wild.

Mitigation direction

  • Upgrade Skipper to version 0.24.0 or later.
  • Confirm ExternalName support is disabled unless explicitly required.
  • If ExternalName is required, allow-list approved targets.
  • Use regular-expression allow-lists only as advised by vendor guidance.
  • Review Kubernetes RBAC for Ingress and ExternalName Service creation rights.

Validation and detection

  • Inventory clusters using Skipper as an Ingress controller.
  • Check deployed Skipper versions for releases before 0.24.0.
  • Identify namespaces where users can create both Ingress and ExternalName Services.
  • Review existing ExternalName Services referenced by Ingress routes.
  • Verify configured allow-lists match approved internal and external targets.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-441: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24470 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2026-24470Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
zalandoskipper< 0.24.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-441 · source CWE mapping

Unintended Proxy or Intermediary ('Confused Deputy')

Unintended Proxy or Intermediary ('Confused Deputy') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.