{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-55675","id":"CVE-2026-55675","title":"Salty documentation workflow executes fork-controlled Python build hooks with deployment secrets","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 requ","descriptionLong":"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.","published":"2026-10-13T15:15:25.023Z","updated":"2026-10-28T02:30:35.307442107Z","reserved":"2026-06-17T00:05:03.778Z","status":"Deferred","rejected":false,"assigner":"GitHub_M","metric":{"version":"3.1","score":10,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","rating":"critical","source":"GitHub_M"},"metrics":[{"version":"3.1","score":10,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","rating":"critical","source":"GitHub_M"},{"version":"3.1","score":10,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","rating":"critical","source":"github.com"},{"version":"3.1","score":10,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","rating":"critical","source":"OSV"}],"rating":"critical","products":["saltyorg docs"],"affectedProducts":[{"vendor":"saltyorg","product":"docs","defaultStatus":null,"versions":[{"version":"< 649c9aea2daef1168eeb0415b44e65dbbde9f220","status":"affected"}],"platforms":[]}],"packages":[],"cwes":["CWE-94","CWE-829","CWE-1357"],"aliases":["GHSA-wr2h-fpxm-ff4x"],"references":[{"url":"https://github.com/saltyorg/docs/security/advisories/GHSA-wr2h-fpxm-ff4x","tags":["x_refsource_CONFIRM","exploit","advisory"]},{"url":"https://github.com/saltyorg/docs/commit/649c9aea2daef1168eeb0415b44e65dbbde9f220","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55675.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55675","tags":["advisory"]}],"patchReferenced":true,"fixAvailable":true,"exploitReferenced":true,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"poc","automatable":"yes","technicalImpact":"total"},"epss":0.00427,"epssPercentile":0.37733,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-55675","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55675","ok":true,"note":"Deferred"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-55675","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-55675","ok":true,"note":"scored 2026-11-19"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}