# Rancher Vulnerable to Cross-site Request Forgery (CSRF)

Advisory record · `GHSA-xhg2-rvm8-w2jh`

- **Identifiers:** `GHSA-xhg2-rvm8-w2jh` · `CVE-2019-13209` · `GO-2022-0755`
- **State:** Confirmed
- **Severity:** CVSS 8.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html) · [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md) · [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 18 May 2021
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 May 2021, 15:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/rancher/rancher` (Go): affected `>=2.0.0, <2.0.16 || >=2.1.0, <2.1.11 || >=2.2.0, <2.2.5`; fixed in `2.0.16`, `2.1.11`, `2.2.5`

## Machine-written summary

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

> Rancher versions 2.0.0 before 2.0.16, 2.1.0 before 2.1.11, and 2.2.0 before 2.2.5 are vulnerable to cross-site websocket hijacking. An attacker can lure a logged-in user to a third-party site they control, then run commands against the Kubernetes API of clusters managed by Rancher with the victim's permissions. Upgrade to 2.0.16, 2.1.11, 2.2.5 or later.

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

- 8.7 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.011, the 66th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:44 UTC: First seen by agentprime
- 31 Oct 2026, 14:44 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xhg2-rvm8-w2jh)

## Sources

- [GitHub Advisory Database: GHSA-xhg2-rvm8-w2jh](https://github.com/advisories/GHSA-xhg2-rvm8-w2jh)
- [OSV: GHSA-xhg2-rvm8-w2jh](https://osv.dev/vulnerability/GHSA-xhg2-rvm8-w2jh)
- <https://nvd.nist.gov/vuln/detail/CVE-2019-13209>
- <https://github.com/rancher/rancher/commit/0ddffe484adccb9e37d9432e8e625d8ebbfb0088>
- <https://forums.rancher.com/t/rancher-release-v2-2-5-addresses-rancher-cve-2019-13209/14801>
- <https://github.com/rancher/rancher>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xhg2-rvm8-w2jh>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xhg2-rvm8-w2jh/>. Everything for agents: <https://agentprime.io/llms.txt>.
