Path Traversal in github.com/k3s-io/k3s (CVE-2026-54250)
Summary
Path traversal in github.com/k3s-io/k3s (CVE-2026-54250). Data can be tampered with by attackers.
Original description
The description as published by the source.
K3s: ZIP Archive Path Traversal Vulnerability in etcd Snapshot Decompression in github.com/k3s-io/k3s.
NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.
(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)
The additional affected modules and versions are: github.com/k3s-io/k3s before v1.33.10, from v1.34.0-rc1 before v1.34.6, from v1.35.0-rc1 before v1.35.3.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54250 has been found in github.com/k3s-io/k3s.
Data can be tampered with by attackers. CVSS score: 5.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/k3s-io/k3s CVE-2026-54250" on the vendor's site.
CVE-2026-54250 (github.com/k3s-io/k3s) — CWE-22 / CVSS v3 5.8
Attack vector: local
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/k3s-io/k3s.
Check the vendor advisory for the affected versions of github.com/k3s-io/k3s.
Severity: Medium (CVSS 5.8/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/k3s-io/k3s' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/k3s-io/k3s' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/k3s-io/k3sを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- web github.com