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

GitHub · Authorization and tenant boundaries

GitHub fork collaboration applied inconsistent authorization

GitHub checked fork-collaboration permissions differently when a setting was created and when it was changed. This could give an unauthorized user write access to affected public forks. The researcher reports a USD 20,000 award for this first finding in the article.

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

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

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

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

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