Quick answers
- Is CVE-2026-12567 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-12567 being exploited in the wild.
- How severe is CVE-2026-12567?
- Low severity, with a CVSS score of 3.1, published 17 June 2026.
- Which products and versions are affected?
- bbot (PyPI) >= 2.0.0, <= 2.8.4, ECOSYSTEM:introduced=2.0.0,fixed=2.8.5.
- Is there a fix for CVE-2026-12567?
- Yes. bbot (PyPI): upgrade to 2.8.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-12567 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-12567?
- Check whether you run bbot (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- bbot (PyPI): upgrade to 2.8.5 or later
pip install "bbot>=2.8.5"
Technical details
The github_workflows module in BBOT (up to version 2.8.4) is vulnerable to an improper link resolution (CWE-59) flaw. The module constructs local directory paths using repository names without verifying if any path components are symbolic links. A local attacker with access to the scan directory can pre-plant a symlink at a predictable output path. When the tool executes, it follows the symlink, causing workflow data to be written to an attacker-chosen location. A fix was introduced in commit 16d9c42 which implements path validation to ensure no components between the trusted output directory and the target folder are symlinks.
Affected products
- Black Lantern Security BBOT 2.0.0 to 2.8.4
Identifiers
- CVE-2026-12567
- GHSA-rvp7-w75q-9fv2
- PYSEC-2026-2394
Timeline
- 2026-06-17: disclosed
- 2026-06-17: advisory
- 2026-06-17: patched: Fixed in commit 16d9c42b6