Arbitrary file write via symlinked output path
Published Jun 17, 2026 · Updated Jun 17, 2026
Path traversal in Black Lantern Security BBOT 2.0.0 through 2.8.4 allows local users to redirect workflow-data writes. The github_workflows module joins untrusted repository owner and name values beneath output_dir, then creates directories and writes logs or artifacts without rejecting symbolic-link path components. Exploitation requires access to the shared scan directory and user interaction; a planted link redirects BBOT's write to an attacker-chosen filesystem location.
Summary
What happened
Path traversal in Black Lantern Security BBOT 2.0.0 through 2.8.4 allows local users to redirect workflow-data writes. The github_workflows module joins untrusted repository owner and name values beneath output_dir, then creates directories and writes logs or artifacts without rejecting symbolic-link path components. Exploitation requires access to the shared scan directory and user interaction; a planted link redirects BBOT's write to an attacker-chosen filesystem location.
The record
- CVE
- CVE-2026-12567
- Published
- Jun 17, 2026
- Updated
- Jun 17, 2026
- Vendor
- Black Lantern Security
- Product
- BBOT
- Classifications
- CWE-59, CAPEC-132
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 17, 2026CVE publishedPublication date reported by the CVE source.
- Jun 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <=<=2.8.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo