Root cause
Contributor status was treated as enough reason to trust workflows running on persistent self-hosted infrastructure. The researcher examined approval rules, runner reuse and build privileges together. Outside contributions were not adequately separated from trusted image production.
Demonstrated impact
With contributor access under the affected configuration, the researcher demonstrated infrastructure access and exposure of build secrets. Compromise of distributed runner images remained a possible consequence, not a demonstrated result, because the intervening production controls were unknown.
What to check for
- Separate untrusted contribution processing from privileged build infrastructure and secrets.
- Bind review to the workflow being executed; prior contribution history is not continuing authorization.
- Use isolated disposable execution environments and independently verify release provenance.
Award and evidence
How the award was verified, and what the record does not establish
One report. GitHub’s official January 2017 article (updated June 2021) explicitly denominates standard bounties in USD; current platform guidelines corroborate context, not this individual award. Earlier researcher post explicitly says paid.
- Payment is researcher-reported, not independently audited.
- The reviewed HackerOne currency guideline is the current page, not a preserved 2023 policy snapshot.
- Resolution on November 14 does not establish an exact final remediation date.
Timeline
- Published
- 2023-12-20explicit · Detailed article date.
- Public Disclosure
- 2023-12-16explicit · Earlier public summary; not the detailed article date.
- Reported
- 2023-07-22explicit
- Awarded
- 2023-11-14explicit
- Paid
- 2023-11-14explicit
- Mitigated
- 2023-07-25explicit · Detailed timeline: initial mitigations. Earlier summary says immediate fixes July 26; final technical fix date remains unknown.
Related cases
- Angular automation trust and cache isolation weakness
Google · Software supply-chain security · USD 31,337
- GitHub package-source trust allowed dependency confusion
GitHub · Software supply-chain security · USD 20,000
- GitHub Actions trust depended on invalid repository references
GitHub · Software supply-chain security · USD 25,000
- GitHub comparison output lacked source-repository authorization
GitHub · Authorization and tenant boundaries · USD 10,000
- GitHub unsafe reflection crossed method and credential boundaries
GitHub · Injection and untrusted input · USD 75,000
Sources
- One Supply Chain Attack to Rule Them All - Poisoning GitHub's Runner ImagesAdnan Khan · reviewed 2026-10-02
- Welcome to my blog - there is more to come!Adnan Khan · reviewed 2026-10-02
- Vulnerability Disclosure GuidelinesHackerOne · reviewed 2026-10-02
- Bug bounty anniversary promotion: Bigger bounties in January and FebruaryNeil Matatall / GitHub · reviewed 2026-10-02
Record reviewed 2026-10-02. Snapshot af2809c308fc. Open the complete JSON contract.