saltyorg docs Code Injection Flaw (CVE-2026-55675) Rated CVSS 10
A newly published critical vulnerability in saltyorg docs carries a CVSS score of 10. Here is what is affected and how to respond.
Key points
- CVE-2026-55675 affects saltyorg docs.
- CVSS 10 (Critical).
- No exploitation confirmed yet.
saltyorg docs is affected by CVE-2026-55675, a code injection that the National Vulnerability Database rates 10 out of 10.
At a glance
- CVE
- CVE-2026-55675
- Product
- saltyorg docs
- CVSS
- 10 Critical
- Weakness
- code injection
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: 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 wit
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Saltyorg | docs | < 649c9aea2daef1168eeb0415b44e65dbbde9f220 |
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-55675
- Patch scores alone ignore context like network exposure and asset criticality.
- You must map vulnerabilities to specific business risks to prioritize correctly.
- Continuous exposure data replaces static scanning for accurate prioritization.
Prioritize vulnerabilities by actual exploitability and business impact, not by theoretical severity scores. Update your asset context and exposure data continuously to maintain accurate risk rankings.
Step-by-step guide: Risk Based Vulnerability Management: Prioritize Fixes by Actual Threat
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-55675?
CVE-2026-55675 is a code injection vulnerability in saltyorg docs.
How severe is CVE-2026-55675?
It has a CVSS score of 10 Critical.
Is CVE-2026-55675 being exploited?
There is no public confirmation of exploitation at the time of publication.
