Categories
CVE-2026-14966 low CVSS 3.1

Path Traversal in bbot (CVE-2026-14966)

Summary

Path traversal in bbot (CVE-2026-14966). Risk of unauthorized operations or information disclosure. Exploitable via unarchive. Mitigation: upgrade to 3.0.0 or later.

Original description

The description as published by the source.

BBOT's unarchive module rejects archives containing symlink entries before extraction, but for zip and 7z archives it failed to detect symlinks whose listing carries a DOS-attribute prefix before the unix mode, as produced by legacy versions of p7zip. Such an archive, downloaded and extracted during a scan (for example via filedownload), bypassed the guard and caused an attacker-controlled symlink to be written into the extraction directory. The effect is limited to planting the symlink (its target is not written through), and only hosts using such a legacy p7zip build are affected; current mainline 7-Zip is not.

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-14966 has been found in bbot.
Attackers can target a specific entry point like unarchive over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: upgrade bbot to 3.0.0 or later.
If unsure, ask your IT team or search "bbot CVE-2026-14966" on the vendor's site.

CVE-2026-14966 (bbot) — CWE-22 / CVSS v3 3.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: unarchive / filedownload
Patched: 3.0.0 — 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.

❓ What is the problem

Path traversal (CWE-22) exists in bbot. Attackers reach the vulnerable code path via unarchive without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of bbot. Attack surface: unarchive / filedownload.

🔥 Severity

Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.0.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify
    grep -r 'bbot' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で bbot を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade bbot to 3.0.0

    ステージング環境で 3.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip bbot
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0"}]}]
PyPI bbot
[{"type":"ECOSYSTEM","events":[{"introduced":"2.3.1"},{"fixed":"3.0.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details