CVE-2026-55675
- Source
- https://cve.org/CVERecord?id=CVE-2026-55675
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-55675.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-55675
- Aliases
-
- GHSA-wr2h-fpxm-ff4x
- Published
- 2026-10-13T15:15:25Z
- Modified
- 2026-10-15T02:47:28Z
- Severity
-
- 10.0 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H CVSS Calculator
- Summary
- Salty documentation workflow executes fork-controlled Python build hooks with deployment secrets
- Details
-
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.
- Database specific
{ "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-1357", "CWE-829", "CWE-94" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55675.json" }- References