Path Traversal in tpwd/ke_search (CVE-2026-46724)
Summary
Path traversal in tpwd/ke_search (CVE-2026-46724). Risk of unauthorized operations or information disclosure. Exploitable via ke_search. Mitigation: upgrade to 4.6.7 or later.
Original description
The description as published by the source.
The file indexer does not normalize the configured directory path. A backend user with permission to edit indexer configurations can index documents from arbitrary locations on the server file system through path traversal sequences.
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-46724 has been found in tpwd/ke_search.
Attackers can target a specific entry point like ke_search over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade tpwd/ke_search to 4.6.7 or later.
If unsure, ask your IT team or search "tpwd/ke_search CVE-2026-46724" on the vendor's site.
CVE-2026-46724 (tpwd/ke_search) — CWE-22
Attack surface: ke_search
Patched: 4.6.7 — 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 tpwd/ke_search. Attackers reach the vulnerable code path via ke_search.
Check the vendor advisory for the affected versions of tpwd/ke_search. Attack surface: ke_search.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.6.7.
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 'tpwd/ke_search' . 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 'tpwd/ke_search' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tpwd/ke_searchを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade tpwd/ke_search to 4.6.7ステージング環境で 4.6.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory typo3.org
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web packagist.org