All vulnerabilities

Servers and applications

CVE-2026-55998

Cluster Existence Oracle via Unauthenticated Import Endpoint

Severity
Medium 5.3
Published
31 Jul 2026
Last changed
3 Aug 2026
Added to UpHeron
3 Nov 2026
Fixed in
2.11.16, 2.12.12, 2.13.8, 2.14.4
Exploit chance
0.3% in the next 30 daysHigher than 28% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Response discrepancy (CWE-204)
Attack
Over the network · No login needed · No user action needed
Attacker can
Read some data
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Also known as
GHSA-23h9-rr79-r3gh
Sources
Project advisories (GitHub)

Description

A vulnerability in Rancher's unauthenticated cluster import endpoint allows an external attacker to enumerate valid cluster IDs and determine whether a cluster is configured with private registry secrets.

The endpoint /v3/import/{token}_{clusterId}.yaml retrieves the cluster object before validating the token. When a valid cluster ID references a cluster that has private registry secrets configured, a nil pointer dereference in pkg/systemtemplate/private_registry.go causes the request to return HTTP 502 Bad Gateway. For cluster IDs that do not exist, the endpoint returns HTTP 200. This observable difference in response codes constitutes a reliable enumeration oracle.

An unauthenticated attacker with network access to the Rancher API can exploit this behavior to:

  • Enumerate valid Rancher cluster IDs
  • Identify which clusters are configured with private registry secrets
  • Fingerprint the infrastructure for use in follow-on attacks
From rancher/rancher's security advisory. Shortened; the full text is there.

Workarounds

If upgrading to a patched version is not immediately possible, operators can reduce exposure by restricting network access to the Rancher API (/v3/import/) to trusted networks using a firewall, reverse proxy, or network policy, so that unauthenticated requests from untrusted sources cannot reach the endpoint.

There is no configuration change within Rancher that fully mitigates this issue without upgrading.

Workarounds as given by rancher/rancher's security advisory.

Affected software

SoftwareAffected versions
RancherServers and applications · github:rancher/rancher
  • From 2.11.0 before 2.11.16
  • From 2.12.0 before 2.12.12
  • From 2.13.0 before 2.13.8
  • From 2.14.0 before 2.14.4

About Rancher

Complete container management platform

From its GitHub repository.
Teams using it daily
More than 30,000Rancher
Docker Hub pulls
320,721,144Docker Hub, 15 Nov 2026
GitHub stars
26,057GitHub, 15 Nov 2026
Forks
3,226GitHub, 15 Nov 2026
Latest release
v2.15.3GitHub, 15 Nov 2026
Released
29 Oct 2026GitHub
License
Apache-2.0GitHub
First published on GitHub
7 Nov 2014GitHub

Release lines

ReleaseLatestSecurity fixes
2.152.15.3Until 27 Feb 2028
2.142.14.7Until 10 Oct 2027
2.132.13.11Until 17 Jun 2027
2.122.12.15Until 28 Feb 2027
2.112.11.19Ended 24 Oct 2026
2.102.10.12Ended 19 Jun 2026

From endoflife.date.

References