CVE-2026-55675Salty documentation workflow executes fork-controlled Python build hooks with deployment secrets
Updated under an hour ago ()
Does this affect you?
It affects saltyorg docs. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.43%, higher than 36% of scored CVEs.
Do this next
Free account, 1 product
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
- 10.0 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- Weakness (CWE)
- CWE-94, CWE-829, CWE-1357
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.43% (percentile 36)
- Assigned by
- GitHub_M
- NVD analysis
- Deferred
- Record last updated
- Oct 13, 2026
- First seen by InfoSec Signals
- Oct 13, 2026
Affected products
saltyorg docs saltyorg:docs (from the name) | before 649c9aea2daef1168eeb0415b44e65dbbde9f220 | CNA record |
References
- https://github.com/saltyorg/docs/security/advisories/GHSA-wr2h-fpxm-ff4xx-refsource-confirm
- https://github.com/saltyorg/docs/commit/649c9aea2daef1168eeb0415b44e65dbbde9f220x-refsource-misc
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.