CVE-2026-55675
CRITICALDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 36% of all known CVEs.
References
Related Vulnerabilities
Other CWE-94 (Code Injection) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-9841 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2015-1635 | Critical | 9.8 | 100% | KEV | - |
| CVE-2022-22954 | Critical | 9.8 | 100% | KEV + Ransom | - |
| CVE-2025-49704 | High | 8.8 | 100% | KEV + Ransom | Fix |
| CVE-2025-3248 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2021-22204 | Medium | 6.8 | 100% | KEV | Fix |
Common questions
How do I fix CVE-2026-55675?
No published fix for CVE-2026-55675 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-55675 being actively exploited?
Not that we know of. CVE-2026-55675 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.43% is the estimated probability that it will be exploited in the next 30 days. That is higher than 36% of all scored CVEs.
How severe is CVE-2026-55675?
CVE-2026-55675 has a CVSS v3 base score of 10.0, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-55675
Markdown
[](https://tridentstack.com/cve/CVE-2026-55675)HTML
<a href="https://tridentstack.com/cve/CVE-2026-55675"><img src="https://tridentstack.com/cve/badge/CVE-2026-55675.svg" alt="CVE-2026-55675"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-13.