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
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
- Google Mamba temporary outputs lacked access isolation
Google · Authorization and tenant boundaries · USD 37,604.40
- Google Firefly confused worker authority and storage boundaries
Google · Authorization and tenant boundaries · USD 60,000
- Google Application Integration mixed resource and service authority
Google · Authorization and tenant boundaries · USD 75,000
- Google support API exposed customer and agent data
Google · Authorization and tenant boundaries · USD 14,337
- GitHub package-source trust allowed dependency confusion
GitHub · Software supply-chain security · USD 20,000
- GitHub unsafe reflection crossed method and credential boundaries
GitHub · Injection and untrusted input · USD 75,000
Sources
- Messing with GitHub’s fork collaboration for fun and profitTeddy Katz · reviewed 2026-10-02
- GitHub Enterprise Server 3.0.1 security fixesGitHub · reviewed 2026-10-02
Record reviewed 2026-10-02. Snapshot af2809c308fc. Open the complete JSON contract.