This vulnerability arises because the Salty documentation repository’s GitHub Actions workflow checks out content from untrusted fork pull requests and installs Python dependencies before executing build hooks. An attacker controlling a fork can supply malicious setup.py or PEP 517 build hook code that runs with the repository’s elevated permissions, allowing the execution of arbitrary code. The privileged secrets exposed in the workflow, such as CF_API_TOKEN, GH_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY, and a write‑capable GITHUB_TOKEN, can be disclosed or used for further compromise. This results in full remote code execution within the context of the repository’s protected workflow, with potential for comprehensive system compromise.

The affected product is the Salty documentation repository (organization saltyorg, product docs). Prior to commit 649c9aea2daef1168eeb0415b44e65dbbde9f220, the workflow definition in .github/workflows/trigger-pr-build.yml and build-pr.yml allowed fork commits to be pulled and installed. No specific version numbers are provided, but the vulnerability exists in the repository state before the aforementioned commit.

The CVSS score of 10 indicates critical severity. The EPSS score is not available, and the issue is not listed in the CISA KEV catalog. The attack requires the attacker to create a pull request from a fork, provide malicious buildhook content, and trigger the workflow. Once triggered, the privileged secrets are accessed and can be exfiltrated or misused, resulting in compromise of the repository and potentially connected infrastructure. The vulnerability would not be exploitable without the attacker’s ability to supply the forked content and trigger the workflow, making the exploitation conditions high in prerequisite but low in detection risk.