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

GitHub · Authorization and tenant boundaries

GitHub GraphQL collaboration changes lacked author consent

One GitHub API allowed collaboration consent to change without the pull-request author's permission. A base-repository maintainer could consequently gain unauthorized write access to a contributor's branch. This second finding received its own researcher-reported USD 10,000 award.

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

Root cause

One API path omitted the pull-request-author entitlement required to change collaboration consent.

Demonstrated impact

A base-repository maintainer could gain unauthorized write access to a contributor branch.

What to check for

  • Keep collaboration consent separate from ordinary metadata privileges.
  • Enforce identical ownership rules across API implementations.

Award and evidence

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

Separate report and award, initially marked duplicate then reopened after its distinct fix requirement was confirmed.

  • Award remains researcher-reported; vendor release notes corroborate the distinct CVE and remediation.

Timeline

Published
2021-03-10explicit
Reported
2021-01-24explicit
Awarded
2021-03-02explicit
Fixed
2021-01-28explicit · github.com deployment; Enterprise Server releases followed March 2, 2021.

Related cases

All 19 cases in Authorization and tenant boundaries

Sources

  1. Messing with GitHub’s fork collaboration for fun and profitTeddy Katz · reviewed 2026-10-02
  2. GitHub Enterprise Server 3.0.1 security fixesGitHub · 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