Path Traversal in bbot (CVE-2026-12565)
Summary
Path traversal in bbot (CVE-2026-12565). Data can be tampered with by attackers. Mitigation: upgrade to 2.8.5 or later.
Original description
The description as published by the source.
The unarchive internal module's archive extraction commands perform no code-level validation on extracted file paths, relying entirely on the behavior of external tools (e.g. GNU tar) which varies by platform. While CVE-2025-10284 addressed git-specific RCE vectors, the underlying archive extraction path traversal was never fixed. On systems with GNU tar < 1.34 (Ubuntu 20.04, Debian Buster, CentOS 7, many Docker base images), a malicious archive can write files outside the intended extraction directory.
Source: GitHub Security Advisories (Global) 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-12565 has been found in bbot.
Data can be tampered with by attackers. CVSS score: 5.3/10.
What to do: upgrade bbot to 2.8.5 or later.
If unsure, ask your IT team or search "bbot CVE-2026-12565" on the vendor's site.
CVE-2026-12565 (bbot) — CWE-22 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.8.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 bbot.
Check the vendor advisory for the affected versions of bbot.
Severity: Medium (CVSS 5.3/10). Data can be tampered with by attackers.
Update to 2.8.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 'bbot' . 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 'bbot' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
bbotを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade bbot to 2.8.5ステージング環境で 2.8.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com