Quick answers
- Is CVE-2026-12568 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-12568 being exploited in the wild.
- How severe is CVE-2026-12568?
- Medium severity, with a CVSS score of 6.5, published 17 June 2026.
- Which products and versions are affected?
- bbot (PyPI) >= 2.1.0, <= 2.8.5, ECOSYSTEM:introduced=2.1.0,fixed=2.8.6.
- Is there a fix for CVE-2026-12568?
- Yes. bbot (PyPI): upgrade to 2.8.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-12568 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-12568?
- 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.6 or later
pip install "bbot>=2.8.6"
Technical details
A path traversal vulnerability (CWE-22) exists in the postman_download.py module of BBOT versions 2.1.0 through 2.8.5. The module uses the 'name' field from the Postman API to construct local directory paths using pathlib without proper sanitization. An attacker can create a malicious Postman workspace with a name containing traversal sequences (e.g., '../'). When a BBOT user attempts to download this workspace, the application resolves the path outside of the intended output directory, enabling arbitrary file writes on the host system. The issue was addressed in commit 36bc208 by implementing 'tagify' on the workspace name and verifying that the resolved path remains relative to the intended output directory.
Affected products
- Black Lantern Security BBOT 2.1.0 to 2.8.5
Identifiers
- CVE-2026-12568
- GHSA-m54h-vhf9-3w3m
- PYSEC-2026-2393
Timeline
- 2026-06-17: disclosed
- 2026-06-17: advisory
- 2026-06-17: patched: Fixed in commit 36bc20818