Finding and attribution
The ready_for_review.yml workflow interpolated pull request branch data into shell commands in jobs with write-all permissions, enabling code execution through untrusted branch names.
Product: U.S. Department of Veterans Affairs vets-api GitHub Actions. AI system: GitHub Security Lab AI agent. Team / organization: GitHub Security Lab.
CVE identifiers: Not established in the cited evidence.
AI and human contribution (source account): GHSL explicitly credits its AI agent and CodeQL jointly; it does not separate their contributions. Reported and fixed 2025-08-13. The advisory does not name a CVE.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The advisory documents the issue and fix; it does not claim exploitation in the wild.
Remediation status: fix documented. GHSL says the affected workflow was fixed on 2025-08-13. No released version or CVE is given.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 19 Dec 2025. AI attribution dated 19 Dec 2025. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: code execution.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
Case-level evidence: code execution.
Prerequisites / affected scope: A user-controlled pull request/workflow branch name is evaluated in shell commands in the affected GitHub Actions workflow, allowing code injection during those workflow runs..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: GHSL says the affected workflow was fixed on 2025-08-13. No released version or CVE is given.