The github_workflows module of BBOT fails to normalize the ".." component during a path‑containment check, allowing a written artifact to be placed two directories above the configured output location. The location that is written to is determined by the operator, so the attacker cannot arbitrarily choose where the file is deposited, but the ability to write outside the intended sandbox still introduces the risk of overwriting or inserting malicious content into files that lie above the output folder.

Black Lantern Security BBOT, specifically the github_workflows module that processes artifact downloads from arbitrary CODE_REPOSITORY URLs.

The CVSS score of 3.1 indicates low severity, and the EPSS score of less than 1% suggests a very low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog, reinforcing its low priority. Exploitation requires an attacker to control the operator provides; thus, if the operator’s environment allows arbitrary repository inputs, an attacker could cause the module to write a file outside the intended directory, potentially affecting system integrity or overwriting critical files. Given the limited scope and low probability, the overall risk remains low but should not be ignored in environments that treat the output directory contents as sensitive.