vulns.co
/
GKData.io MCP and API Buy me a coffee

GitHub · Software supply-chain security

GitHub Actions trust depended on invalid repository references

GitHub Actions could give an unauthorized workflow access to repository secrets and write permissions because repository references were not checked consistently. The researcher reports a USD 25,000 award for this finding.

Read the original writeupUSD 25,000 reported award · Reviewed 2026-10-02

Root cause

GitHub checked that a pull request's base reference was a branch when creating it, but not consistently when that reference changed. Actions relied on that assumption when deciding which workflows could receive repository secrets and write permissions.

Demonstrated impact

Repository secrets and write authority could become available to an unauthorized workflow.

What to check for

  • Check that a pull request's base reference identifies a valid branch whenever it changes and before using it to grant workflow privileges.
  • Keep repository secrets confined to explicitly trusted execution contexts.

Award and evidence

USD 25,000Bug Bounty · Researcher Reported
How the award was verified, and what the record does not establish

Single finding; the later 2022 follow-up earned USD 7,500 and is excluded.

  • Award is reported by the cited source; cash settlement is not independently audited.

Timeline

Published
2021-03-17explicit
Reported
2021-02-04explicit
Awarded
2021-03-03explicit
Fixed
2021-03-02explicit · GitHub Enterprise Server 3.0.1 release; github.com was fixed earlier in February, without an exact final timestamp in the source.

Related visual models

Related cases

All 4 cases in Software supply-chain security

Sources

  1. Stealing arbitrary GitHub Actions secretsTeddy Katz · reviewed 2026-10-02

Record reviewed 2026-10-02. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software