---
id: "CVE-2026-88809"
kind: "vulnerability"
aliases: ["CVE-2026-88809"]
title: "SUSE Rancher Manager: authenticated users can make the server request destinations the /meta/proxy allowlist should block (SSRF)"
severity: "high"
cvss: 7.6
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: [{"name": "rancher", "fixed": ["2.11.19", "2.12.15", "2.13.11", "2.14.7", "2.15.3"], "affected": ">=2.11.0 <2.11.19, >=2.12.0 <2.12.15, >=2.13.0 <2.13.11, >=2.14.0 <2.14.7, >=2.15.0 <2.15.3", "ecosystem": "vendor"}]
ecosystems: []
tags: ["infrastructure", "kubernetes", "rancher", "self-hosted", "ssrf"]
not_affected_if: ["auth-required", "managed-hosting", "patched-version", "version-outside-affected-ranges"]
published_at: "2026-11-02T16:17:44+00:00"
first_seen_at: "2026-11-02T16:24:05+00:00"
updated_at: "2026-11-02T16:30:19+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-88809", "first_seen_at": "2026-11-02T16:24:05+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-11-02T16:30:19+00:00"}]
---

# SUSE Rancher Manager: authenticated users can make the server request destinations the /meta/proxy allowlist should block (SSRF)

Rancher Manager's /meta/proxy endpoint logs when a destination fails its allowlist check but still forwards the request anyway. An attacker who can reach the endpoint can make the Rancher server send requests to destinations the allowlist was meant to block.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:rancher affected >=2.11.0 <2.11.19, >=2.12.0 <2.12.15, >=2.13.0 <2.13.11, >=2.14.0 <2.14.7, >=2.15.0 <2.15.3 fixed 2.11.19, 2.12.15, 2.13.11, 2.14.7, 2.15.3

## How to check

Check your Rancher Manager version. Affected: >=2.15.0 <2.15.3, >=2.14.0 <2.14.7, >=2.13.0 <2.13.11, >=2.12.0 <2.12.15, >=2.11.0 <2.11.19 (older EOL lines may be affected). Then check how Rancher is exposed: a direct path to Rancher (a pod in the local cluster reaching the Rancher Service, networkExposure.type none with an L4 load balancer, tls: external passthrough, hostPort/hostNetwork) leaves the endpoint reachable; the default Helm Ingress behind nginx, Traefik, Envoy or HAProxy blocks the needed request form. Logs show 'Failed to proxy:' for each attempt, but normal rejections log the same line, so logs cannot confirm abuse. Also check whether the Rancher server can reach cloud metadata (AWS IMDSv1).

## Fix

Upgrade Rancher Manager to 2.15.3, 2.14.7, 2.13.11, 2.12.15 or 2.11.19 (matching your minor line). Server-side only, no breaking changes. If you suspect prior abuse, rotate credentials reachable from the Rancher server, including cloud instance-metadata credentials.

## Timeline

- 2026-11-02T16:24:05+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-88809
- 2026-11-02T16:30:19+00:00 analyst — Read GHSA-f9gf-wh3x-jx3v. Fixed versions, auth required, workarounds (HTTP-aware proxy, NetworkPolicy, egress limits) confirmed from vendor text. No exploitation or PoC seen; did not search social.

## Documents

- [advisory] Vendor advisory: github.com https://github.com/rancher/rancher/security/advisories/GHSA-f9gf-wh3x-jx3v

## From the sources

A security vulnerability exists in the SUSE Rancher Manager meta proxy endpoint (/meta/proxy). This endpoint is intended to forward requests only to  destinations that appear on a configured allowlist. The allowlist decision was evaluated in a  place where it could not stop a request from being forwarded, so a rejected destination was logged but the request was still handed to the proxy's transport. This affects SUSE Rancher 2.15.0 up to 2.15.3, 2.14.0 up to 2.14.7, 2.13.0 up to 2.13.11, 2.12.0 up to 2.12.15, 2.11.0 up to 2.11.19 and potentially older EOL versions.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_