CVE-2026-55675: CWE-94: Improper Control of Generation of Code ('Code Injection') in saltyorg docs
Description
CVE-2026-55675 is a critical code injection vulnerability in the saltyorg docs repository that allowed attacker-controlled code execution during the build process of the docs.saltbox.dev website. The flaw existed because the workflow checked out untrusted fork commits before installing dependencies, enabling malicious setup.py or build hooks to run with privileged tokens. This could lead to secret disclosure and repository compromise. The issue was fixed by commit 649c9aea2daef1168eeb0415b44e65dbbde9f220.
CVSS v3.1
Score 10.0critical
Affected software
saltyorg
docs
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The saltyorg docs repository's GitHub Actions workflows previously allowed code injection via untrusted fork commits in pull requests. Specifically, the trigger-pr-build.yml workflow recorded the fork commit in an artifact, and the build-pr.yml workflow checked out that commit before running pip install. This allowed an attacker controlling the fork to supply malicious setup.py or PEP 517 build hooks that executed with elevated privileges, including access to sensitive tokens such as CF_API_TOKEN, GH_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY, and a write-capable GITHUB_TOKEN. The vulnerability was not due to the repository-fork guard but due to the execution of attacker-controlled code in the privileged workflow environment. The issue was resolved by commit 649c9aea2daef1168eeb0415b44e65dbbde9f220.
Potential Impact
Successful exploitation allows an attacker to execute arbitrary code in the context of the repository's privileged GitHub Actions workflow, leading to disclosure of sensitive secrets and potential full compromise of the repository and its resources. The CVSS score is 10.0 (critical), indicating maximum impact on confidentiality, integrity, and availability.
Mitigation Recommendations
This vulnerability has been fixed by commit 649c9aea2daef1168eeb0415b44e65dbbde9f220. Users should update their workflows to include this fix. No further action is required if this commit or a later version is applied.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-17T00:05:03.778Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ace4bf22cdf04f6567ca2a6
Added to database: 10/13/2026, 15:19:14 UTC
Last enriched: 10/13/2026, 15:33:18 UTC
Last updated: 10/13/2026, 15:34:05 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.