SaltStack Docs Vulnerability Exposes Secrets via Forked Pull Requests
Attackers could steal credentials from the SaltStack documentation repository by injecting malicious code into a pull request from a forked project.
Key points
- The flaw allows execution of attacker-controlled installation scripts in privileged workflows.
- Sensitive tokens including CF_API_TOKEN and GITHUB_TOKEN were accessible to the attacker.
- The issue is fixed in commit 649c9aea2daef1168eeb0415b44e65dbbde9f220 of the saltyorg docs repo.
Security teams analyzing the SaltStack documentation repository discovered a critical flaw that allowed attackers to extract sensitive credentials. The vulnerability, tracked as CVE-2026-55675, carried a CVSS score of 10, which the National Vulnerability Database rates as critical. The issue existed in the way the project handled pull requests from forked versions of the repository. According to the NVD record, the flaw allowed malicious code to run in a privileged environment where secret tokens were available.
In plain English
The documentation website for SaltStack, hosted at docs.saltbox.dev, is built and deployed using automated workflows. These workflows run on GitHub when contributors submit changes. The problem arose because the system checked out and installed software from untrusted fork commits before running the main build. An attacker could submit a pull request containing a malicious setup file. When the main repository’s automated system processed this request, it executed the attacker’s code with high privileges.
The background
The vulnerable workflow involved two specific files in the GitHub Actions configuration. The first file, trigger-pr-build.yml, recorded information from an untrusted fork commit into an artifact named pr_info. The second file, build-pr.yml, was responsible for the actual build. This second workflow checked out the commit referenced in the artifact. It then ran a command to install dependencies listed in requirements.txt. Because the source code came from the attacker’s fork, the attacker controlled what was installed.
What changes now
The maintainers of the saltyorg docs repository have resolved the issue. The fix is contained in commit 649c9aea2daef1168eeb0415b44e65dbbde9f220. Any version of the repository prior to this commit is considered affected. The National Vulnerability Database notes that the vulnerability is not related to a missing repository-fork guard. Instead, the path to exploitation required the attacker to control the content of the fork, specifically by supplying malicious build hooks or setup files that executed during the installation phase.
What made it possible
Organizations must recognize that automated build pipelines often trust inputs from external contributors. When a workflow checks out code from a forked repository and executes installation commands, it creates a dangerous execution context. Attackers exploit this by injecting malicious scripts into package configuration files. These scripts run with the same privileges as the main workflow, granting access to stored secrets. Teams should treat all external code as untrusted until it is verified and merged into the main branch.
What to do and how to stay safe: SaltStack
- Review GitHub Actions workflows to ensure that code from forked pull requests is never checked out and executed in jobs that have access to secrets.
- Implement strict permission controls on tokens used in automated pipelines, ensuring they have the minimum necessary scope for their specific tasks.
- Audit build scripts and dependency installation steps to confirm that they do not execute arbitrary code from unverified sources before the code is approved.
- Monitor for unusual activity in repository workflows, such as unexpected network connections or secret access patterns during the processing of pull requests.
Step-by-step guide: Automatic Updates Mistakes That Leave Systems Exposed
General security guidance from the RedTeam Monitor newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Does this vulnerability affect the main SaltStack software?
According to the NVD record, this vulnerability affects the saltyorg documentation repository and the docs.saltbox.dev website, not the core SaltStack software itself.
Is there a patch available for this issue?
Yes, the vulnerability is fixed in commit 649c9aea2daef1168eeb0415b44e65dbbde9f220 of the affected repository.
What specific secrets were exposed by this flaw?
The NVD record states that the attacker could access CF_API_TOKEN, GH_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY, and a write-capable GITHUB_TOKEN.
