Skip to content

VNX-GH-102: SHA pin does not match its version comment

uses: owner/repo@<sha> # vX.Y.Z, but vX.Y.Z resolves to a different commit.

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

Reviewers and update bots read the version comment, not the SHA. A SHA that does not match its comment either predates an update that only changed the comment, or was swapped deliberately to run a different commit under a trusted-looking version.

Severity High
Confidence high
CWE CWE-345, CWE-451
Command vulnetix gha actions, vulnetix gha audit
Needs action refs. Without them the rule is reported as not evaluated, never as passed.

Remediation

Re-pin to the commit the intended version resolves to, and update the comment and SHA together.

Run only this rule

vulnetix gha actions --rule VNX-GH-102

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_actions.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.