Is this vulnerability remotely exploitable?

Yes, but only if an attacker can both influence Kubernetes resources (Ingress + ExternalName Service) and send traffic through the affected Skipper ingress. In many setups, this means a tenant or namespace admin within the cluster rather than an arbitrary external internet user.

What level of access does an attacker need?

The attacker must be able to create or modify Kubernetes Ingress resources processed by Skipper and Services of type `ExternalName`. Cluster role and namespace policies that grant these permissions effectively define who can exploit the issue.

What is the safest general fix pattern?

The most robust pattern is to disable ExternalName-based routing for Skipper or restrict it with strict allow-lists for target hostnames and domains. Combine that with network policies that limit Skipper's outbound connectivity to only those destinations required for legitimate traffic.

Severity:

HIGH RISK

(8.1)

Server-Side Request Forgery / Internal Service Exposure (CWE-918, CWE-441) via ExternalName in Skipper Ingress Controller

CVE-2026-24470

Published:

Jan 26, 2026

Status:

Awaiting Analysis

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-306

CRITICAL RISK

CRITICAL

(9.8)

Missing Authentication for Forgot-Password Email Change API (CWE-306)

Account Takeover / Loss of Account Control

February 17, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in node-sonos-http-api TTS Provider for macOS

Remote Code Execution on the Server Host

February 17, 2026

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF) / Internal Service Exposure

CWE:

CWE-441;CWE-918

Impact:

Unauthorized Access to Internal Services and Network Resources

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF) / Internal Service Exposure

CWE:

CWE-441;CWE-918

Impact:

Unauthorized Access to Internal Services and Network Resources

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Server-Side Request Forgery / Internal Service Exposure (CWE-918, CWE-441) via ExternalName in Skipper Ingress Controller

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.8)

Missing Authentication for Forgot-Password Email Change API (CWE-306)

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in node-sonos-http-api TTS Provider for macOS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare