# CVE-2026-25705: Rancher Extensions have arbitrary file access via path traversal

> Attackers can exploit path traversal in Rancher UI extensions to overwrite binaries or configuration, leading to code execution and privilege escalation.

- **Severity:** High 8.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-5v3h-x4wf-5c35, GO-2026-5154

## What is CVE-2026-25705?

CVE-2026-25705 is a high-severity path traversal vulnerability in SUSE rancher, published on 13 May 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been identified in [Rancher's Extensions](https://ranchermanager.docs.rancher.com/integrations-in-rancher/rancher-extensions) where malicious code can be injected in Rancher through a path traversal in the `compressedEndpoint` field inside a `UIPlugin` deployment. A malicious UI extension could abuse that to:  *  Overwrite Rancher binaries or configuration to inject code.

  *  Write to /var/lib/rancher/ to tamper with cluster state.

  *  If hostPath volumes are mounted, write to the host node filesystem.

  *  Use this issue to chain with other attack vectors.

Weakness: CWE-35 (Path Traversal: '.../...//')

## Which versions are affected by CVE-2026-25705?

9 open source packages ship an affected version, including github.com/rancher/rancher.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/rancher/rancher` | Go | All versions | None |
| `github.com/rancher/rancher` | Go | From 2.10.11 | 2.11.13 |
| `github.com/rancher/rancher` | Go | From 2.10.11 | 2.11.13 |
| `github.com/rancher/rancher` | Go | From 2.12.0 | 2.12.9 |
| `github.com/rancher/rancher` | Go | From 2.12.0 | 2.12.9 |
| `github.com/rancher/rancher` | Go | From 2.13.0 | 2.13.5 |
| `github.com/rancher/rancher` | Go | From 2.13.0 | 2.13.5 |
| `github.com/rancher/rancher` | Go | From 2.14.0 | 2.14.1 |
| `github.com/rancher/rancher` | Go | From 2.14.0 | 2.14.1 |

## How do I fix CVE-2026-25705?

Upgrade github.com/rancher/rancher to a fixed version for your release line: 2.11.13, 2.12.9, 2.13.5 or 2.14.1.

## Is CVE-2026-25705 being exploited?

There is no known exploitation of CVE-2026-25705 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25705 and fix it if it is affected.

What it is: CVE-2026-25705 is a high-severity path traversal vulnerability in SUSE rancher, published on 13 May 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-25705 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/rancher/rancher (Go): affected all versions; no fix listed
- github.com/rancher/rancher (Go): affected from 2.10.11; fixed in 2.11.13
- github.com/rancher/rancher (Go): affected from 2.10.11; fixed in 2.11.13
- github.com/rancher/rancher (Go): affected from 2.12.0; fixed in 2.12.9
- github.com/rancher/rancher (Go): affected from 2.12.0; fixed in 2.12.9
- github.com/rancher/rancher (Go): affected from 2.13.0; fixed in 2.13.5
- github.com/rancher/rancher (Go): affected from 2.13.0; fixed in 2.13.5
- github.com/rancher/rancher (Go): affected from 2.14.0; fixed in 2.14.1
- github.com/rancher/rancher (Go): affected from 2.14.0; fixed in 2.14.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25705/ (Markdown: https://insights.sbomify.com/CVE-2026-25705/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25705
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25705
- OSV: https://osv.dev/vulnerability/CVE-2026-25705

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25705/
Summaries are generated and may contain mistakes; the official description above is the record.