Skip to main content
Vulnerability Database/CVE-2026-55675

CVE-2026-55675: Salty Docs Information Disclosure Vulnerability

CVE-2026-55675 is an information disclosure flaw in the Salty documentation repository allowing attackers to access sensitive tokens through malicious fork pull requests. This article covers technical details, impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-55675 Overview

CVE-2026-55675 is a code injection vulnerability in the Salty documentation repository, which builds and deploys the docs.saltbox.dev website. The flaw resides in two GitHub Actions workflows: .github/workflows/trigger-pr-build.yml and .github/workflows/build-pr.yml. An attacker-controlled fork pull request can inject malicious build hooks that execute inside a privileged workflow_run context, exposing repository secrets. The vulnerability is fixed in commit 649c9aea2daef1168eeb0415b44e65dbbde9f220.

Critical Impact

Attackers can execute arbitrary code in a privileged workflow context and exfiltrate CF_API_TOKEN, GH_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY, and a write-capable GITHUB_TOKEN, enabling follow-on repository compromise.

Affected Products

  • saltyorg/docs repository workflows prior to commit 649c9aea2daef1168eeb0415b44e65dbbde9f220
  • .github/workflows/trigger-pr-build.yml pull-request trigger workflow
  • .github/workflows/build-pr.yml secret-bearing workflow_run job

Discovery Timeline

  • 2026-10-13 - CVE-2026-55675 published to NVD
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-55675

Vulnerability Analysis

The Salty documentation repository uses a two-workflow pattern common for building fork pull requests. The trigger-pr-build.yml workflow runs on untrusted fork events, records the fork commit SHA into a pr_info artifact, and uploads it. A second workflow, build-pr.yml, runs with workflow_run triggers and inherits access to repository secrets.

The privileged workflow reads the artifact, checks out the attacker-supplied fork commit, and executes pip install -r requirements.txt. Because pip install invokes arbitrary setup.py scripts and PEP 517 build backends, any attacker-controlled Python packaging code executes with full secret access.

This issue is classified as [CWE-94] Improper Control of Generation of Code (Code Injection). The vulnerability does not stem from the repository-fork guard logic; the exploitation path requires attacker control of fork repository contents, not simple artifact metadata tampering.

Root Cause

The root cause is executing untrusted fork code inside a workflow_run job that holds privileged secrets. Checking out an attacker-controlled commit and running pip install on an attacker-authored requirements.txt, setup.py, or pyproject.toml grants arbitrary code execution.

Attack Vector

An attacker opens a pull request from a fork containing a malicious setup.py or PEP 517 build hook. When the privileged workflow runs, the build hook executes and reads environment secrets, including CF_API_TOKEN, GH_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY, and the write-scoped GITHUB_TOKEN. The attacker can then exfiltrate credentials and push to the base repository. See the GitHub Security Advisory GHSA-wr2h-fpxm-ff4x for technical details.

Detection Methods for CVE-2026-55675

Indicators of Compromise

  • Unexpected outbound network connections from GitHub Actions runners during pip install steps on pull-request builds
  • Workflow logs showing checkout of fork commit SHAs inside workflow_run jobs that reference repository secrets
  • Unauthorized commits, releases, or Cloudflare API changes correlated with recent fork pull-request activity
  • New or modified setup.py, pyproject.toml, or requirements.txt files in incoming fork pull requests

Detection Strategies

  • Audit GitHub Actions workflow runs for workflow_run jobs that check out ${{ github.event.workflow_run.head_sha }} or artifact-derived commits before installing dependencies
  • Review audit logs for secret usage patterns from pull-request-triggered builds, especially pushes using GITHUB_TOKEN with write scope
  • Correlate Cloudflare and GitHub API logs for anomalous requests from CI IP ranges

Monitoring Recommendations

  • Enable GitHub audit log streaming and alert on secret-scoped workflow executions tied to fork events
  • Monitor repository settings for unexpected branch protection or workflow permission changes
  • Rotate and alert on usage of CF_API_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY, and personal access tokens stored as workflow secrets

How to Mitigate CVE-2026-55675

Immediate Actions Required

  • Update the Salty docs repository to commit 649c9aea2daef1168eeb0415b44e65dbbde9f220 or later
  • Rotate CF_API_TOKEN, GH_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY, and any other secrets previously exposed to the vulnerable workflows
  • Review recent pull-request-triggered workflow runs for signs of exploitation and revert any unauthorized commits

Patch Information

The maintainers resolved the issue in commit 649c9aea2daef1168eeb0415b44e65dbbde9f220. Organizations maintaining forks or derivative workflows should apply equivalent changes. Full advisory details are available in GHSA-wr2h-fpxm-ff4x.

Workarounds

  • Disable the vulnerable workflow_run build job until the patch is applied
  • Remove secret access from any workflow that checks out untrusted fork code
  • Replace pip install -r requirements.txt on untrusted content with a sandboxed build runner that lacks access to repository secrets
  • Require manual approval for workflows executing against first-time contributors using the GitHub repository setting for fork pull-request approvals
bash
# Configuration example: restrict GITHUB_TOKEN permissions in build-pr.yml
permissions:
  contents: read
  pull-requests: read

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.