GHSL-2026-225: Artifact metadata injection in actions/attest
Published Sep 16, 2026
·Updated
The commit-dist.yml workflow trusts an artifact-supplied branch name. An external contributor can exploit this trust boundary violation to push attacker-controlled dist/ content to a target repository branch.
Event History
Sep 16, 2026
Advisory Published
via GitHub Security Lab·12:00 AM
Data Sourced
via GitHub Security Lab·12:00 AM
Description
Frequently Asked Questions
1
Who can exploit this issue?
An external contributor can exploit it if they can provide an artifact whose metadata includes an attacker-controlled branch name.
2
What must be present for exploitation to succeed?
The target must use the commit-dist.yml workflow and trust the artifact-supplied branch name when deciding where to push dist/ content. The attacker needs a way to supply the relevant artifact metadata through the workflow's trust boundary.
3
What is the likely impact of successful exploitation?
Successful exploitation allows attacker-controlled dist/ content to be pushed to a target repository branch.