Skip to content
Fencer Intel
high 8.4

CVE-2026-25705 json

Rancher Extensions have arbitrary file access via path traversal

published 6mo ago modified 14d ago also GHSA-5v3h-x4wf-5c35 , GO-2026-5154 , EUVD-2026-29915

cvss
8.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/rancher/rancher 2.11.13, 2.12.9, 2.13.5, 2.14.1
  • SUSE rancher 2.11.13, 2.12.9, 2.13.5, 2.14.1
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2026-25705 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
5mo ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.4 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
GitHub 3.1 8.4 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/rancher/rancher
>=2.14.0, <2.14.1
>=2.13.0, <2.13.5
>=2.12.0, <2.12.9
>=2.10.11, <2.11.13
all versions
2.14.1
2.13.5
2.12.9
2.11.13

Affected products

  • SUSE rancher

Classification

Weakness
  • CWE-35 Path Traversal: '.../...//'

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.