GHSL-2026-204: Artifact poisoning in the SPIFFE SPIRE reviewer assignment workflow
Published Sep 16, 2026
·Updated
The assign-reviewer-review-apply workflow extracts a fork-controlled artifact over trusted executable code. An external contributor can replace an imported module and execute JavaScript with issue and pull request write permissions.
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 workflow issue?
An external contributor who can submit fork-controlled content to the repository can exploit it by replacing an imported module in the artifact consumed by the workflow.
2
What permissions could attacker-controlled code receive?
The injected JavaScript can run with issue and pull request write permissions.
3
Which workflow behavior needs to be changed to prevent exploitation?
The workflow should not extract or execute a fork-controlled artifact in a trusted context. Artifact contents imported from external contributor forks must be treated as untrusted.