Root cause
Permission checks differed between creation and modification of the same collaboration setting.
Demonstrated impact
An unauthorized user could obtain write access to affected public forks.
What to check for
- Centralize entitlement checks across mutation paths.
- Verify that only an authorized owner can grant collaboration privileges.
Award and evidence
How the award was verified, and what the record does not establish
First report only; the separately awarded CVE-2021-22863 is a different record.
- Award is reported by the cited source; cash settlement is not independently audited.
Timeline
- Published
- 2021-03-10explicit
- Reported
- 2021-01-22explicit
- Awarded
- 2021-03-02explicit
- Fixed
- 2021-01-27explicit · 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
Record reviewed 2026-10-02. Snapshot af2809c308fc. Open the complete JSON contract.