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

GitHub · Software supply-chain security

GitHub runner-image builds shared persistent infrastructure with untrusted workflows

GitHub runner-image builds shared persistent infrastructure with workflows that had not earned the same level of trust. The researcher demonstrated infrastructure access and exposed build secrets, and reports a $20,000 payment. Compromise of distributed runner images remained a possibility, not a demonstrated result, because intervening production controls were unknown.

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

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

USD 20,000Bug Bounty · Researcher Reported
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

All 4 cases in Software supply-chain security

Sources

  1. One Supply Chain Attack to Rule Them All - Poisoning GitHub's Runner ImagesAdnan Khan · reviewed 2026-10-02
  2. Welcome to my blog - there is more to come!Adnan Khan · reviewed 2026-10-02
  3. Vulnerability Disclosure GuidelinesHackerOne · reviewed 2026-10-02
  4. 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.

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

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