Advisory record · GHSA-5587-2x54-jj6h

Skipper's routesrv-no-auth component: All routesrv API Endpoints Lack Authentication

CVSS 5.7 MediumEPSS 0.0034 · 27th percentile

Published by the GitHub Advisory Database at 17 Jul 2026, 21:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/zalando/skipperGo<0.27.130.27.13
Identifiers
GHSA-5587-2x54-jj6h · CVE-2026-54246 · GO-2026-6018
Weakness (CWE)
CWE-306
Published
17 Jul 2026
Updated
22 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Skipper's routesrv component, in github.com/zalando/skipper versions before 0.27.13, serves route configuration and Redis/Valkey shard addresses over plain HTTP without any authentication. An attacker who can reach routesrv on the network, such as a compromised pod in the same Kubernetes cluster, can read cluster-wide route and cache topology data. Upgrade to version 0.27.13 or later. Restricting network access to routesrv with Kubernetes NetworkPolicies reduces exposure but does not add authentication.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.7 Medium 3.1 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0034, the 27th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:57 UTC First seen by agentprime
  2. 31 Oct 2026, 14:57 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.