{"api_version":"1","generated_at":"2026-10-28T00:57:31+00:00","cve":"CVE-2026-55675","urls":{"html":"https://cve.report/CVE-2026-55675","api":"https://cve.report/api/cve/CVE-2026-55675.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-55675","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-55675"},"summary":{"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 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.","state":"PUBLISHED","assigner":"GitHub_M","published_at":"2026-10-13 16:17:21","updated_at":"2026-10-13 17:17:42"},"problem_types":["CWE-94","CWE-829","CWE-1357","CWE-94 CWE-94: Improper Control of Generation of Code ('Code Injection')","CWE-829 CWE-829: Inclusion of Functionality from Untrusted Control Sphere","CWE-1357 CWE-1357: Reliance on Insufficiently Trustworthy Component"],"metrics":[{"version":"3.1","source":"security-advisories@github.com","type":"Secondary","score":"10","severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","baseScore":10,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"CHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"10","severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","data":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":10,"baseSeverity":"CRITICAL","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"CHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://github.com/saltyorg/docs/security/advisories/GHSA-wr2h-fpxm-ff4x","name":"https://github.com/saltyorg/docs/security/advisories/GHSA-wr2h-fpxm-ff4x","refsource":"134c704f-9b21-4f2e-91b3-4a467353bcc0","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/saltyorg/docs/commit/649c9aea2daef1168eeb0415b44e65dbbde9f220","name":"https://github.com/saltyorg/docs/commit/649c9aea2daef1168eeb0415b44e65dbbde9f220","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-55675","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55675","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"saltyorg","product":"docs","version":"affected < 649c9aea2daef1168eeb0415b44e65dbbde9f220","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-55675","options":[{"Exploitation":"poc"},{"Automatable":"yes"},{"Technical Impact":"total"}],"role":"CISA Coordinator","timestamp":"2026-10-13T16:22:32.466720Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-10-13T16:22:51.021Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"references":[{"tags":["exploit"],"url":"https://github.com/saltyorg/docs/security/advisories/GHSA-wr2h-fpxm-ff4x"}],"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"product":"docs","vendor":"saltyorg","versions":[{"status":"affected","version":"< 649c9aea2daef1168eeb0415b44e65dbbde9f220"}]}],"descriptions":[{"lang":"en","value":"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."}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":10,"baseSeverity":"CRITICAL","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"CHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-94","description":"CWE-94: Improper Control of Generation of Code ('Code Injection')","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-829","description":"CWE-829: Inclusion of Functionality from Untrusted Control Sphere","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-1357","description":"CWE-1357: Reliance on Insufficiently Trustworthy Component","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-10-13T15:15:25.023Z","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M"},"references":[{"name":"https://github.com/saltyorg/docs/security/advisories/GHSA-wr2h-fpxm-ff4x","tags":["x_refsource_CONFIRM"],"url":"https://github.com/saltyorg/docs/security/advisories/GHSA-wr2h-fpxm-ff4x"},{"name":"https://github.com/saltyorg/docs/commit/649c9aea2daef1168eeb0415b44e65dbbde9f220","tags":["x_refsource_MISC"],"url":"https://github.com/saltyorg/docs/commit/649c9aea2daef1168eeb0415b44e65dbbde9f220"}],"source":{"advisory":"GHSA-wr2h-fpxm-ff4x","discovery":"UNKNOWN"},"title":"Salty documentation workflow executes fork-controlled Python build hooks with deployment secrets"}},"cveMetadata":{"assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","assignerShortName":"GitHub_M","cveId":"CVE-2026-55675","datePublished":"2026-10-13T15:15:25.023Z","dateReserved":"2026-06-17T00:05:03.778Z","dateUpdated":"2026-10-13T16:22:51.021Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-13 16:17:21","lastModifiedDate":"2026-10-13 17:17:42","problem_types":["CWE-94","CWE-829","CWE-1357","CWE-94 CWE-94: Improper Control of Generation of Code ('Code Injection')","CWE-829 CWE-829: Inclusion of Functionality from Untrusted Control Sphere","CWE-1357 CWE-1357: Reliance on Insufficiently Trustworthy Component"],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","baseScore":10,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"CHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":3.9,"impactScore":6}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-10-13T16:22:32.466720Z","id":"CVE-2026-55675","options":[{"exploitation":"poc"},{"automatable":"yes"},{"technicalImpact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"55675","Ordinal":"1","Title":"Salty documentation workflow executes fork-controlled Python bui","CVE":"CVE-2026-55675","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"55675","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"Salty documentation workflow executes fork-controlled Python bui"}]}}}