mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 19:38:46 -05:00
[PR #23064] [CLOSED] fix: pin 49 unpinned action(s),extract 4 unsafe expression(s) to env vars #42636
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/23064
Author: @dagecko
Created: 3/26/2026
Status: ❌ Closed
Base:
main← Head:runner-guard/fix-ci-security📝 Commits (1)
3f1ca43fix: pin 49 unpinned action(s),extract 4 unsafe expression(s) to env vars📊 Changes
2 files changed (+60 additions, -53 deletions)
View changed files
📝
.github/workflows/docker-build.yaml(+59 -52)📝
.github/workflows/release-pypi.yml(+1 -1)📄 Description
Fix: CI/CD Security Vulnerabilities in GitHub Actions
Hi! Runner Guard, an open-source
CI/CD security scanner by Vigilant Cyber Security,
identified security vulnerabilities in this repository's GitHub Actions workflows.
This PR applies automated fixes where possible and reports additional findings
for your review.
Fixes applied (in this PR)
.github/workflows/docker-build.yaml.github/workflows/docker-build.yaml.github/workflows/release-pypi.ymlAdvisory: additional findings (manual review recommended)
| Rule | Severity | File | Description |
| RGS-003 | high |
.github/workflows/docker-build.yaml| Filename Injection via Git Diff or File Listing || RGS-003 | high |
.github/workflows/docker-build.yaml| Filename Injection via Git Diff or File Listing || RGS-003 | high |
.github/workflows/docker-build.yaml| Filename Injection via Git Diff or File Listing || RGS-003 | high |
.github/workflows/docker-build.yaml| Filename Injection via Git Diff or File Listing || RGS-003 | high |
.github/workflows/docker-build.yaml| Filename Injection via Git Diff or File Listing || RGS-003 | high |
.github/workflows/docker-build.yaml| Filename Injection via Git Diff or File Listing |Why this matters
GitHub Actions workflows that use untrusted input in
run:blocks, exposesecrets inline, or use unpinned third-party actions are vulnerable to
code injection, credential theft, and supply chain attacks. These are the same
vulnerability classes exploited in the tj-actions/changed-files incident
and subsequent supply chain attacks, which compromised CI secrets across
thousands of repositories.
How to verify
Review the diff — each change is mechanical and preserves workflow behavior:
${{ }}expressions fromrun:blocks intoenv:mappings, preventing shell injection(original version tag preserved as comment)
ACTIONS_RUNNER_DEBUG/ACTIONS_STEP_DEBUGwhich leak secrets in workflow logs
Run
brew install Vigilant-LLC/tap/runner-guard && runner-guard scan .or install from therepo to verify.
Found by Runner Guard | Built by Vigilant Cyber Security | Learn more
If this PR is not welcome, just close it -- we won't send another.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.