Skip to content

VNX-GH-022: Privileged job restores a cache keyed on contributor input

In a pull_request_target, workflow_run or comment-triggered job, a cache key or the cached content is derived from the pull request.

Updated 02 Nov 2026Checked against cli@24498404a, vdb-sca-match@v0.8.14

A key built from the head branch or head SHA lets a contributor choose which entry the privileged job restores; restoring a cache after checking out the pull request saves the contributor’s files under a key later trusted runs restore.

Severity High
Confidence medium
CWE CWE-349, CWE-494
Command vulnetix gha workflows, vulnetix gha audit

Remediation

Key caches only on base-branch content (hashFiles of the base checkout), and do not cache in a job that checked out untrusted code.

Run only this rule

vulnetix gha workflows --rule VNX-GH-022

Scoring

CWSS vector at the rule’s default severity: CWSS:1.0/TI:H/AP:A/AL:A/IC:N/FC:LT/RP:N/RL:A/AV:I/AS:N/IN:A/SC:A/BI:H/DI:H/EX:M/EC:N/P:W. A finding whose severity the repository’s settings moved is scored at its adjusted severity.

All rules: GitHub rules.

Edit this pageSources: vdb-sca-match/ghaudit/rules_workflows.go, cli/internal/ghtasks/docs.go
esc
↑ ↓ move↵ openSearches in your browser. A key like autonomy.max or a code like threshold_required jumps straight to it.