CVE-2026-88809: SUSE Rancher Manager meta proxy allowlist bypass leading to SSRF

CVE-2026-88809 · Severity: high · CVSS 7.6 · Published 2026-11-02

SUSE Rancher Manager is a Kubernetes cluster management platform. An authenticated user can bypass the meta proxy endpoint's allowlist of permitted destinations, allowing them to send requests to internal systems and potentially access sensitive data, cloud credentials, or other resources normally blocked. The vulnerability affects multiple versions of Rancher.

Technologies: Suse Rancher Manager. Vendors: Suse.

Quick answers

Is CVE-2026-88809 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-88809 being exploited in the wild.
How severe is CVE-2026-88809?
High severity, with a CVSS score of 7.6, published 2 November 2026.
Which products and versions are affected?
Suse Rancher Manager 2.15.0 to 2.15.3, 2.14.0 to 2.14.7, 2.13.0 to 2.13.11, 2.12.0 to 2.12.15, 2.11.0 to 2.11.19, and potentially older EOL versions.
Is there a fix for CVE-2026-88809?
Yes: fixed in Rancher 2.15.3, 2.14.7, 2.13.11, 2.12.15, 2.11.19. Until then: Ensure all network paths to the Rancher server go through an HTTP-aware reverse proxy or ingress controller rather than layer 4 load balancers, TLS passthrough, or direct Service access. Additionally, apply NetworkPolicy rules to restrict workload pods from connecting directly to the Rancher Service, and restrict the Rancher server's egress with network policies or security groups to prevent access to internal services and cloud metadata endpoints. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-88809 attacked?
It is attacked over the network.
Am I affected by CVE-2026-88809?
Check whether you run Suse Rancher Manager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: Rancher 2.15.3, 2.14.7, 2.13.11, 2.12.15, 2.11.19

Ensure all network paths to the Rancher server go through an HTTP-aware reverse proxy or ingress controller rather than layer 4 load balancers, TLS passthrough, or direct Service access. Additionally, apply NetworkPolicy rules to restrict workload pods from connecting directly to the Rancher Service, and restrict the Rancher server's egress with network policies or security groups to prevent access to internal services and cloud metadata endpoints.

Technical details

The /meta/proxy endpoint is intended to forward HTTP requests only to allowlisted destinations, but the allowlist validation was performed too late in the request handling—after the request had already been passed to the proxy transport. This allows authenticated users to reach non-allowlisted destinations via server-side request forgery (SSRF). The attacker can control the request method, headers, body, and query string; responses are returned to the user. Preconditions include authentication, HTTP/1.1 request format with full URL in the request line, and a direct network path to the Rancher Service (not through standard reverse proxies like nginx, Traefik, Envoy, or HAProxy).

Affected products

  • SUSE Rancher Manager 2.15.0 to 2.15.3, 2.14.0 to 2.14.7, 2.13.0 to 2.13.11, 2.12.0 to 2.12.15, 2.11.0 to 2.11.19, and potentially older EOL versions

Timeline

  • 2026-10-29: disclosed
  • 2026-11-02: advisory
  • 2026-10-29: patched: patches released for versions 2.15.3, 2.14.7, 2.13.11, 2.12.15, 2.11.19

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.