CVE-2026-55675
10 CRITICALpublic exploit availablePublished 2026-10-13 · Updated 2026-10-13
AI risk analysis
- Summary
- A GitHub Actions workflow vulnerability allows untrusted fork commits to execute malicious Python code with high-privilege secrets, potentially leading to complete repository compromise and secret disclosure.
- Exploitability
- Easy to exploit with a malicious fork PR that includes attacker-controlled setup.py or build hooks, requiring only the ability to create a fork and submit a pull request to the target repository.
- Blast radius
- High impact as attackers can access and potentially exfiltrate multiple sensitive API keys and tokens including CF_API_TOKEN, GH_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY, and a write-capable GITHUB_TOKEN, enabling further compromise of the repository and connected services.
- Detection
- Monitor for unusual workflow_run events in .github/workflows/build-pr.yml that check out commits from untrusted forks, particularly those with modified setup.py or build hooks in the pr_info artifact.
- Prioritized remediation
- Upgrade to commit 649c9aea2daef1168eeb0415b44e65dbbde9f220 which fixes the workflow to properly validate fork commits before checking them out.
Analysis generated locally by garnet-coder (no data left the box). AI-assisted — verify against primary sources before acting.
NVD description
The Salty documentation repository builds and deploys the docs.saltbox.dev website. Prior to commit 649c9aea2daef1168eeb0415b44e65dbbde9f220, .github/workflows/trigger-pr-build.yml records an untrusted fork commit in the pr_info artifact, and the secret-bearing workflow_run job in .github/workflows/build-pr.yml checks out that commit before running pip install -r requirements.txt. A fork pull request can therefore supply attacker-authored setup.py or PEP 517 build hooks whose installation code executes in the privileged base-repository workflow with CF_API_TOKEN, GH_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY, and a write-capable GITHUB_TOKEN, allowing secret disclosure and follow-on compromise. The vulnerability is not caused by the repository-fork guard, and the demonstrated path requires attacker control of fork content rather than merely the artifact metadata. This vulnerability is fixed with commit 649c9aea2daef1168eeb0415b44e65dbbde9f220.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Weaknesses
CWE-94, CWE-829, CWE-1357
Public exploit & PoC references
All references
Source data: NVD (nvd.nist.gov), public domain. Exploit-DB.ai adds local AI analysis for defensive use only.
Related CVEs
- HIGHCVE-2026-12171PoC
- HIGHCVE-2026-103670PoC
- HIGHCVE-2026-105816
- HIGHCVE-2026-107589
- HIGHCVE-2026-107812PoC
- HIGHCVE-2026-84691
- CRITICALCVE-2026-89078
- HIGHCVE-2026-92470
Related by shared AI tags and CWE weakness class. Browse the full archive.