Path Traversal in BBOT (CVE-2026-14967)
Summary
Path traversal in BBOT (CVE-2026-14967). Risk of unauthorized operations or information disclosure. Exploitable via github_workflows.
Original description
The description as published by the source.
BBOT's github_workflows module could be induced to write a downloaded artifact outside its configured output directory: its path-containment check did not resolve .., so a crafted CODE_REPOSITORY URL could traverse out of the intended folder. The write is bounded to two directory levels above the output location and its target is determined by the operator's configuration, not the attacker.
Source: NIST National Vulnerability Database NVD
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-14967 has been found in BBOT.
Attackers can target a specific entry point like github_workflows over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "BBOT CVE-2026-14967" on the vendor's site.
CVE-2026-14967 (BBOT) — CWE-22 / CVSS v3 3.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: github_workflows / CODE_REPOSITORY
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. Attackers reach the vulnerable code path via github_workflows without authentication.
Check the vendor advisory for the affected versions of BBOT. Attack surface: github_workflows / CODE_REPOSITORY.
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
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 し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- patch github.com