Path Traversal in Tookie (CVE-2026-42866)
Summary
Path traversal in Tookie (CVE-2026-42866). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.1fix or later.
Original description
The description as published by the source.
Tookie is a advanced OSINT information gathering tool. Prior to 4.1fix, modules/modules.py's write_txt, write_csv, write_json, and (commented-but-shipping) scan_file helpers open their output as open(f"{user}."), where user comes unsanitized from the -u CLI flag or any line of a -U usernames file. A username that contains path-separator sequences (.., /, , or an absolute path) causes tookie-osint to write the scan output to an arbitrary path the invoking user has write permission for. This vulnerability is fixed in 4.1fix.
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-42866 has been found in Tookie.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Tookie to 4.1fix or later.
If unsure, ask your IT team or search "Tookie CVE-2026-42866" on the vendor's site.
CVE-2026-42866 (Tookie) — CWE-22
Patched: 4.1fix — 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 Tookie.
Check the vendor advisory for the affected versions of Tookie.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.1fix.
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 'Tookie' . 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 'Tookie' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Tookieを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Tookie to 4.1fixステージング環境で 4.1fix に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov