Key points
- CVE-2026-55675 enables secret disclosure via untrusted fork commits.
- Attackers can run privileged workflows using stolen tokens.
- Fix is available in commit 649c9aea2daef1168eeb0415b44e65dbbde9f220.
Malicious code injected through forked pull requests can execute within the privileged SaltStack documentation repository workflows, stealing sensitive tokens. According to the NVD record for CVE-2026-55675, this critical vulnerability allows attackers to compromise the build process by supplying their own setup files. The flaw affects the saltyorg docs repository prior to the specific fix commit, exposing credentials like CF_API_TOKEN and GITHUB_TOKEN.
The vulnerability arises because the trigger workflow records untrusted fork commit data in an artifact. The subsequent build workflow checks out that specific commit before installing dependencies. This sequence allows attacker-authored setup.py files or PEP 517 build hooks to run installation code in the base repository environment. Consequently, attackers gain access to write-capable tokens and other secrets stored in the workflow context.
What we know
The NVD describes the weakness as involving code injection and improper handling of untrusted data. The affected component is the .github/workflows/trigger-pr-build.yml file, which passes data to .github/workflows/build-pr.yml. The vulnerability is not related to repository-fork guards but requires attacker control of the fork content itself. The fix, identified by commit hash 649c9aea2daef1168eeb0415b44e65dbbde9f220, addresses the unsafe checkout behavior.
What analysts watch for
Teams usually monitor CI/CD logs for unusual dependency installations or unexpected network connections during pull request builds. Analysts examine workflow artifacts to verify that only trusted base repository code is executed. They check whether workflows properly isolate untrusted fork content from privileged steps. Security teams also review token permissions to ensure minimal scope, preventing lateral movement if a build environment is compromised.
What to do and how to stay safe: SaltStack
- Update the SaltStack docs repository to commit 649c9aea2daef1168eeb0415b44e65dbbde9f220 immediately.
- Audit existing GitHub Actions workflows for similar patterns where untrusted forks trigger privileged jobs.
- Rotate all secrets exposed in the affected repository, including CF_API_TOKEN and MKDOCS_GIT_COMMITTERS_APIKEY.
- Review access logs for any unauthorized actions performed using the stolen GITHUB_TOKEN.
Step-by-step guide: Security Advisories: Small Business Patching Strategy
General security guidance from the Malware Chronicle newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the severity of CVE-2026-55675?
The NVD rates the vulnerability as Critical with a CVSS score of 10.
How do attackers exploit this flaw?
They submit a fork pull request containing malicious setup.py or build hooks that execute during the dependency installation phase.
Is there a confirmed fix?
Yes, the vulnerability is fixed with commit 649c9aea2daef1168eeb0415b44e65dbbde9f220.
