Path Traversal in OpenWrt (CVE-2026-62947)
Summary
Path traversal in OpenWrt (CVE-2026-62947). Confidential information can be exposed externally. Mitigation: upgrade to 25.12.5 or later.
Original description
The description as published by the source.
OpenWrt is a Linux operating system targeting embedded devices. Prior to 25.12.5, the cgi-download handler in cgi-io authorizes the requested path against the caller's ubus session file ACL before canonicalization, and rpcd session.c uses fnmatch() without FNM_PATHNAME, allowing traversal such as an allowed wildcard prefix followed by ../ to read root-readable files including /etc/shadow. This vulnerability is fixed in 25.12.5.
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-62947 has been found in OpenWrt.
Confidential information can be exposed externally. CVSS score: 4.9/10.
What to do: upgrade OpenWrt to 25.12.5 or later.
If unsure, ask your IT team or search "OpenWrt CVE-2026-62947" on the vendor's site.
CVE-2026-62947 (OpenWrt) — CWE-22 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Patched: 25.12.5 — apply immediately
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 OpenWrt.
Check the vendor advisory for the affected versions of OpenWrt.
Severity: Medium (CVSS 4.9/10). Confidential information can be exposed externally.
Update to 25.12.5.
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 'OpenWrt' . 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 'OpenWrt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
OpenWrtを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade OpenWrt to 25.12.5ステージング環境で 25.12.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- web github.com