How severe is CVE-2026-25705?

CVE-2026-25705 has a CVSS score of 8.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-25705?

CVE-2026-25705 affects the following packages: github.com/rancher/rancher (Go), github.com/rancher/rancher (Go), github.com/rancher/rancher (Go), github.com/rancher/rancher (Go). Ecosystems affected: Go.

How do I fix CVE-2026-25705?

Update github.com/rancher/rancher to 2.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25705 is resolved across your whole dependency graph.

How do I detect CVE-2026-25705 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/rancher, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-25705 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-25705 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-25705 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-25705?

CVE-2026-25705 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-25705?

CVE-2026-25705 is classified as CWE-35 (CWE-35). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-25705 published, and has it been updated?

CVE-2026-25705 was published on May 13, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2026-25705 — rancher

HIGH

CVE-2026-25705 is a high-severity (CVSS 8.4) CWE-35 vulnerability in github.com/rancher/rancher. A fix is available for github.com/rancher/rancher — see the affected versions and patch details below.

Rancher Extensions have arbitrary file access via path traversal

Also known asGHSA-5v3h-x4wf-5c35GO-2026-5154

Published

May 13, 2026

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25705.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐹github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancher

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A vulnerability has been identified in Rancher's 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.

By default only the administrator can deploy UI extensions, unless permissions are granted to other users. It's always recommended to only install extensions that come from sources trusted by the user.

Please consult the associated MITRE CAPEC-126 - Technique - Path Traversal for further information about this category of attack.

Patches

This vulnerability is addressed by ensuring that:

The file defined by the UI Plugin CR's compressedEndpoint has to be created inside the cache directory and cannot contain ../. If that is not possible, the installation will fail and the file won't be created.
The icons referenced by Cluster Repos' index.yaml file always resolves to a file inside the repository directory.

Patched versions of Rancher include releases v2.14.1, v2.13.5, v2.12.9, v2.11.13.

Workarounds

There is no workaround. The user must be careful about which UI Plugins they install.

Resources

If there are any questions or comments about this advisory:

Reach out to the SUSE Rancher Security team for security related inquiries.
Open an issue in the Rancher repository.
Verify with the support matrix and product support lifecycle.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/rancher/rancher`	≥ 2.14.0&&< 2.14.1	2.14.1`go get github.com/rancher/rancher@v2.14.1`
🐹Go	`github.com/rancher/rancher`	≥ 2.13.0&&< 2.13.5	2.13.5`go get github.com/rancher/rancher@v2.13.5`
🐹Go	`github.com/rancher/rancher`	≥ 2.12.0&&< 2.12.9	2.12.9`go get github.com/rancher/rancher@v2.12.9`
🐹Go	`github.com/rancher/rancher`	≥ 2.10.11&&< 2.11.13	2.11.13`go get github.com/rancher/rancher@v2.11.13`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/rancher, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/rancher/rancher to 2.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25705 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Impact 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. By defa

O3 Security · Impact-Aware SCA

Is CVE-2026-25705 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H

CWE Classification

CWE-35CWE-35

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

rancher

6.8/10

Code-Review10/10

Maintained10/10

Branch-Protection5/10

Assessed Nov 2, 2026

Timeline

Disclosed

May 13, 2026

Last updated

Oct 28, 2026

Identifiers

CVE-2026-25705

GHSA-5v3h-x4wf-5c35

GO-2026-5154

References

Advisorygithub.com · CVE 2026 25705.json Advisorygithub.com · GHSA 5v3h x4wf 5c35 Advisorynvd.nist.gov · CVE 2026 25705 Reportbugzilla.suse.com · show bug.cgi Packagegithub.com · rancher

Related vulnerabilities

This CVE is high severity; 8 of 8 other CVEs affecting rancher are rated as high or higher (top: critical).

CVE-2026-41053CVE-2026-44939CVE-2026-41052CVE-2022-31247CVE-2021-36783CVE-2021-25320GHSA-hwm2-4ph6-w6m5CVE-2023-22648

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2026-25705 — rancher

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

Workarounds

Resources

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2026-25705 in your dependencies?