EUVD-2026-37816
GHSA-rvp7-w75q-9fv2
Severity by source
AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N
Local-only symlink attack requires shared-directory write access, victim-triggered scan, and pre-positioned symlink; no confidentiality or availability impact.
Primary rating from Vendor (BLSOPS).
CVSS VectorVendor: BLSOPS
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N
Lifecycle Timeline
2DescriptionCVE.org
The github_workflows module constructs local directory paths from user-controlled repository names without validating for symlinks. A local attacker sharing the scan directory can plant a symlink at the predictable output path, causing workflow data to be written to an attacker-chosen location.
AnalysisAI
Symlink-following path traversal in BBOT's github_workflows module (all versions prior to commit 16d9c42b6) allows a local attacker sharing the scan output directory to redirect workflow artifact writes to an attacker-chosen filesystem location. By planting a symlink at the predictable output path (output_dir/owner/repo) before a scan runs, the attacker causes BBOT to write GitHub workflow data outside the intended directory, achieving a limited file-write primitive. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires four concurrent conditions: (1) the attacker holds a local account with write access to the BBOT scan output directory - typically implying a shared or multi-tenant scanning host; (2) the attacker can predict or observe the target repository owner and name used in the scan in order to construct the correct symlink path before execution; (3) the victim operator actively runs the github_workflows module against the targeted repository (UI:R - exploitation cannot occur without operator-triggered scan execution); and (4) the intended output path does not already exist as a real directory, since a pre-existing real directory would not be replaced by the symlink. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Real-world risk is low and closely aligned with the CVSS 2.2 score. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker with a local account on a shared scanning host determines that an operator is about to scan a GitHub repository with a known owner/name and creates a symlink at output_dir/targetowner/targetrepo pointing to a sensitive directory (such as a system configuration path or another user's home directory) before the scan begins. When the operator runs the github_workflows scan, BBOT follows the symlink without detection and writes downloaded workflow artifacts into the attacker-chosen target path. … |
| Remediation | Update BBOT to a build that includes commit 16d9c42b6 (https://github.com/blacklanternsecurity/bbot/commit/16d9c42b6), which adds symlink validation via _check_output_path() to both artifact collection paths in github_workflows.py. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
More from same product – last 7 days
Arbitrary file write in BBOT's postman_download module enables a remote attacker to write files outside the intended out
Path traversal in BBOT's unarchive internal module enables a malicious archive hosted by attacker-controlled infrastruct
Authentication token leakage in Black Lantern Security's bbot docker_pull module exposes Docker credentials to MITM atta
Share
External POC / Exploit Code
Leaving vuln.today