CVE-2026-24470
Skipper Ingress before 0.24.0 allows internal access via ExternalName routes.
Is CVE-2026-24470 being exploited?
Not confirmed. CVE-2026-24470 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-24470?
CVE-2026-24470 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-24470?
Yes. A fix has been recorded for CVE-2026-24470. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-24470 affect?
CVE-2026-24470 affects Skipper Ingress Controller <= 0.23.x. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-24470?
Upgrade to 0.24.0+; restrict ExternalName usage.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Ingress users with ExternalName rights can reach internal services through Skipper, risking data exposure.
Patch when possible
- affected< 0.24.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.