VNX-GH-103: Pinned commit is not in the action's repository

The pinned SHA exists only in a fork of the action repository.

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

GitHub serves commits from any fork through the parent repository’s URL. An attacker can push malicious code to a fork and propose a pin to that SHA; it looks like owner/repo@ but the commit was never part of owner/repo.


Severity	Critical
Confidence	high
CWE	CWE-345, CWE-494
Command	`vulnetix gha actions`, `vulnetix gha audit`
Needs	action refs. Without them the rule is reported as not evaluated, never as passed.
Mappings	T1195.001

Remediation

Replace the SHA with one that is reachable from a branch or tag of the action repository itself.

Run only this rule

vulnetix gha actions --rule VNX-GH-103

Scoring

CWSS vector at the rule’s default severity: CWSS:1.0/TI:C/AP:A/AL:A/IC:N/FC:LT/RP:N/RL:A/AV:I/AS:N/IN:A/SC:A/BI:C/DI:H/EX:H/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