CVE-2026-54250: k3s · Path Traversal
Affects k3sSource CVE Database V5
Not known to be exploited · CVSS 5.8 Medium · fixed in 1.35.3+k3s1 : update k3s when convenient.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.35.3+k3s1, 1.34.6+k3s1, 1.33.10+k3s1
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.
What to do
Upgrade k3s to 1.35.3+k3s1, 1.34.6+k3s1 or 1.33.10+k3s1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| k3s-iok3s | Affected
| Fixed in
|
| k3s-iok3s | Affected
| Fixed in
|
| k3s-iok3s | Affected
| Fixed in
|
GitHubk3s-io/k3spkg:github/k3s-io/k3sOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to k3s versions 1.35.3+k3s1, 1.34.6+k3s1, or v1.33.10+k3s1 or later, where this path traversal vulnerability is fixed. Until upgraded, avoid restoring etcd snapshots from untrusted or unauthenticated sources to prevent exploitation.
Description
K3s is a fully conformant production-ready Kubernetes distribution. Prior to 1.35.3+k3s1, 1.34.6+k3s1, v1.33.10+k3s1, a path traversal vulnerability exists in K3s's etcd snapshot decompression functionality. Zip files containing archive members with maliciously crafted names can be written to arbitrary locations on the filesystem when an administrator restores the archive as a compressed etcd snapshot. This vulnerability is fixed in 1.35.3+k3s1, 1.34.6+k3s1, v1.33.10+k3s1.