Finding and attribution
The release.yml workflow interpolates a user-controlled workflow-run branch name into a shell assignment in a privileged workflow_run context, creating an arbitrary code execution risk.
Product: cross-platform-actions/action. 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 credits CodeQL and its AI agent; the advisory was published 2025-10-27. It does not give a patch version or separate the tools’ contributions.
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 public advisory documents the vulnerability and disclosure/remediation status. It does not claim exploitation in the wild.
Remediation status: not established. The cited public source does not establish a fix or fixed version.
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 14 Nov 2025. AI attribution dated 14 Nov 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 branch name can inject and execute arbitrary code in the release workflow context when the documented workflow trigger conditions are met..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: The cited public source does not establish a fix or fixed version.