# RKE2 allows privilege escalation in Windows nodes due to Insecure Access Control Lists

Advisory record · `GHSA-x7xj-jvwp-97rv`

- **Identifiers:** `GHSA-x7xj-jvwp-97rv` · `GO-2024-3222`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-269](https://cwe.mitre.org/data/definitions/269.html) · [CWE-732](https://cwe.mitre.org/data/definitions/732.html)
- **Tags:** [Privilege escalation](https://agentprime.io/advisories/tag/privilege-escalation.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 25 Oct 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Oct 2024, 19:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/rancher/rke2` (Go): affected `>=1.27.0, <1.27.15 || >=1.28.0, <1.28.11 || >=1.29.0, <1.29.6 || >=1.30.0, <1.30.2`; fixed in `1.27.15`, `1.28.11`, `1.29.6`, `1.30.2`

## Machine-written summary

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

> RKE2 on Windows nodes, versions 1.27.0 up to 1.27.15, 1.28.0 up to 1.28.11, 1.29.0 up to 1.29.6, and 1.30.0 up to 1.30.2, has weak access control lists on sensitive files. A local user on the node could view or edit those files and escalate privileges. Upgrade to 1.27.15, 1.28.11, 1.29.6, 1.30.2, or 1.31.0 or later; alternatively, apply stricter ACLs to the affected files using the script the advisory references.

Written 1 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

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

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:15 UTC: First seen by agentprime
- 31 Oct 2026, 14:15 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x7xj-jvwp-97rv)

## Sources

- [GitHub Advisory Database: GHSA-x7xj-jvwp-97rv](https://github.com/advisories/GHSA-x7xj-jvwp-97rv)
- [OSV: GHSA-x7xj-jvwp-97rv](https://osv.dev/vulnerability/GHSA-x7xj-jvwp-97rv)
- <https://github.com/rancher/rancher/security/advisories/GHSA-7h8m-pvw3-5gh4>
- <https://github.com/rancher/rke2/security/advisories/GHSA-x7xj-jvwp-97rv>
- <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32197>
- <https://github.com/rancher/rke2>

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-x7xj-jvwp-97rv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x7xj-jvwp-97rv/>. Everything for agents: <https://agentprime.io/llms.txt>.
