CVE-2026-55675

published 13 Oct 2026 · updated 13 Oct 2026

Salty documentation workflow executes fork-controlled Python build hooks with deployment secrets

10.0CriticalCVSS 10.0EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
saltyorg<649c9aea2daef1168eeb0415b44e65dbbde9f220

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-55675 severity on Zeptric[![CVE-2026-55675](https://zeptric.io/badge/cve/CVE-2026-55675.svg)](https://zeptric.io/cve/CVE-2026-55675)