Orgs at Risk: Unpatched Salty Docs Workflows Execute Fork Code, Exposing High-Value Tokens via CVE-2026-55675

The Salty documentation repository contains a critical vulnerability that exposes sensitive credentials through pull requests from forked repositories. Security teams must apply the specific commit fix to prevent attackers from executing arbitrary code within privileged workflows.

What happened

The Salty documentation repository, which builds and deploys the docs.saltbox.dev website, contained a flaw in its GitHub Actions workflows. Prior to commit 649c9aea2daef1168eeb0415b44e65dbbde9f220, the trigger-pr-build.yml workflow recorded untrusted fork commit data in an artifact. The subsequent build-pr.yml job then checked out that specific commit before installing Python requirements.

This sequence allowed an attacker to supply a malicious setup.py or PEP 517 build hook via a forked pull request. When the privileged base-repository workflow installed these requirements, the attacker-authored code executed with access to sensitive environment variables. These variables included CF_API_TOKEN, GH_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY, and a write-capable GITHUB_TOKEN.

The vulnerability stems from CWE-94, CWE-829, and CWE-1357 weaknesses, rated CVSS 10 CRITICAL by the NVD. The issue is not caused by the repository-fork guard but by the execution of untrusted code during the dependency installation phase. The demonstrated attack path requires the attacker to control the content of the fork, not merely the artifact metadata.

Why it matters

The vulnerability allows secret disclosure and follow-on compromise, as stated in the NVD record. The critical severity rating indicates that the flaw is significant. The demonstrated path requires attacker control of fork content rather than merely the artifact metadata.

The flaw highlights the risks of executing untrusted code in privileged contexts. Without the fix, a forked pull request can supply attacker-authored code whose installation code executes in the privileged base-repository workflow.

What happens next

• Apply commit 649c9aea2daef1168eeb0415b44e65dbbde9f220 to the affected Salty docs repository.
• Rotate all exposed secrets, including CF_API_TOKEN, GH_TOKEN, and MKDOCS_GIT_COMMITTERS_APIKEY.
• Review other repositories for similar workflow patterns that check out untrusted fork commits.
• Audit GitHub Actions permissions to ensure minimal privilege for build jobs.

Patch priority

Teams should prioritise updating systems that expose the repository to external pull requests. Begin by identifying any environments that mirror or interact with the affected documentation repository. Apply the fix to these high-exposure systems first to prevent immediate secret theft. Test the updated workflows in a staging environment to ensure functionality remains intact. Back up current configurations before applying changes to allow for rollback if issues arise. Monitor logs for any signs of unauthorised access or unusual workflow executions.

What to do and how to stay safe: Salty

• Verify whether your organisation uses or mirrors the Salty documentation repository.
• Check if your GitHub Actions workflows check out commits from untrusted forks.
• Rotate any secrets that may have been exposed in privileged workflow environments.
• Implement stricter code review processes for pull requests involving workflow changes.

Step-by-step guide: Vulnerability Prioritization: Stop Fixing Everything and Start Fixing What Matters

General security guidance from the AppSec Scoop newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is CVE-2026-55675?

It is a critical vulnerability in the Salty docs repository allowing secret theft via forked pull requests.

Is a fix available?

Yes, the vulnerability is fixed with commit 649c9aea2daef1168eeb0415b44e65dbbde9f220.

Which secrets are at risk?

CF_API_TOKEN, GH_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY, and a write-capable GITHUB_TOKEN are exposed.