CVE-2026-14967 in BBOT
Summary
by MITRE • 07/08/2026
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.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 07/08/2026
The vulnerability in BBOT's github_workflows module represents a path traversal flaw that undermines the security boundaries of the tool's output handling mechanism. This issue stems from insufficient input validation within the path containment checks that govern where downloaded artifacts can be written. The flaw specifically manifests when processing repository URLs that contain relative path components such as ".." which are not properly resolved or sanitized before file system operations are executed.
The technical implementation of this vulnerability allows an attacker to manipulate the CODE_REPOSITORY URL parameter in a way that bypasses the intended directory restrictions. When BBOT processes a crafted repository URL containing parent directory references, the path containment logic fails to normalize these paths properly, enabling arbitrary file system traversal beyond the designated output directory. This behavior creates a significant security risk as it allows potential attackers to write files to locations outside the intended sandboxed environment where BBOT operates.
From an operational impact perspective, this vulnerability could enable adversaries to write malicious files to critical system locations, potentially leading to privilege escalation or persistence mechanisms. The bounded nature of the write operation limits the traversal to only two directory levels above the output location, but this still provides sufficient access to compromise the system's integrity. The target location is determined by operator configuration rather than attacker control, which means that successful exploitation requires a valid repository URL pointing to a controlled artifact, but once achieved, the attacker can inject content into arbitrary locations relative to the configured output directory.
The vulnerability aligns with CWE-22 Path Traversal and specifically relates to improper input validation in file system operations. This weakness falls under the ATT&CK technique T1059 Command and Scripting Interpreter where adversaries might leverage such path traversal vulnerabilities to execute malicious code through compromised repository artifacts. The attack surface is particularly concerning for security automation tools like BBOT that process external inputs from repositories, as they may be used in environments where untrusted code execution could lead to complete system compromise.
Mitigation strategies should focus on implementing robust path normalization and validation mechanisms within the github_workflows module. The solution requires ensuring that all repository URLs undergo proper canonicalization before any file system operations are performed, effectively resolving all ".." references and preventing directory traversal attempts. Additionally, operators should implement strict input validation for CODE_REPOSITORY parameters and consider deploying additional sandboxing measures to limit the scope of potential file system impacts even if path traversal occurs. The module should enforce absolute path checking with proper boundary validation to prevent any writes outside explicitly configured directories regardless of URL content.