CVE-2026-12567 Black Lantern Security CVE debrief

Who should care

Users of Black Lantern Security's BBOT, especially those with shared scan directories, should be aware of this vulnerability and take steps to mitigate it. This includes reviewing and validating symlink handling in the github_workflows module, implementing proper validation for user-controlled repository names, restricting write access to workflow data directories, and monitoring for suspicious symlink creation. BBOT operators and security teams should prioritize this vulnerability due to its potential impact on workflow data integrity and the ease of exploitation by local attackers.

Technical summary

The github_workflows module in BBOT constructs local directory paths from user-controlled repository names without proper symlink validation. This allows a local attacker sharing the scan directory to plant a symlink at the predictable output path. Consequently, workflow data can be written to an attacker-chosen location. The vulnerability has a CVSS score of 2.2 and is classified as LOW severity. The exploitation requires local access to the scan directory and user-controlled repository names.

Defensive priority

Defensive priority should be medium to low due to the LOW severity score and limited attack surface. However, BBOT users with shared scan directories should prioritize mitigation efforts to prevent potential data integrity issues.

Recommended defensive actions

• Review and validate symlink handling in github_workflows module
• Implement proper validation for user-controlled repository names
• Restrict write access to workflow data directories
• Monitor for suspicious symlink creation in shared scan directories
• Apply vendor remediation when available
• Conduct a thorough review of BBOT configurations and github_workflows module usage
• Verify the integrity of workflow data and scan directories for potential exploitation signs

Evidence notes

Evidence is limited but indicates a genuine vulnerability exists in the github_workflows module of Black Lantern Security's BBOT. Further review of the module and BBOT configuration is necessary to fully understand the impact and verify affected scope. Defenders should review the official CVE record and NVD details for CVE-2026-12567, focusing on the LOW severity score and limited attack surface. The vulnerability allows a local attacker to plant a symlink at a predictable output path, causing workflow data to be written to an attacker-chosen location. This can occur when a local attacker shares the scan directory and exploits the lack of symlink validation in user-controlled repository names.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.