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

GitHub · Authorization and tenant boundaries

GitHub OAuth consent failed across request-method semantics

GitHub's request-handling layers disagreed about when an OAuth access grant required user consent. A user visiting a malicious website could unintentionally grant an application access to private GitHub data. The researcher reports a $25,000 award; USD is inferred from official program evidence published or updated outside the award period.

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

Root cause

The framework accepted request semantics that the controller did not expect. Application logic treated that unexpected case as permission to grant access, even though the usual consent checks did not apply. The researcher found the mismatch by comparing the consent screen’s intended action with routing and controller behavior. Every new grant should have required explicit, validated user approval.

Demonstrated impact

The researcher reports that a user visiting a malicious website could unintentionally grant an application access to read or modify private GitHub data. This demonstrates unauthorized delegated access, rather than evidence that the attacker learned the account password or that all unrelated account controls failed.

What to check for

  • Require positive validation of the intended state-changing operation; reject unrecognized alternatives rather than defaulting to a privileged action.
  • Model framework routing, request interpretation and consent enforcement as separate layers whose assumptions must agree.
  • Verify that consent and request-integrity checks remain attached to every path that creates a grant.
  • The source dates the production fix and later Enterprise releases, but does not document the exact patch here; these lessons are defensive recommendations.

Award and evidence

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

Individual report; production fix date is for github.com, with enterprise releases following June 26. The researcher uses $ without an explicit currency. USD is a contextual inference from github-currency-context-2017: GitHub's January 9, 2017 program article, updated June 25, 2021, explicitly names USD. Its publication predates the June 26, 2019 award and its displayed update postdates it; this is non-contemporaneous program-wide context, not proof of this individual award's currency or settlement. No conflicting denomination was found in the reviewed sources.

  • Researcher-reported award; cash settlement is not independently audited.
  • The reported impact requires user interaction. Exact vendor patch implementation and evidence of real-world abuse are not supplied.
  • USD is inferred from a program-wide article published in 2017 and updated in 2021, not contemporaneous individual-award evidence from 2019. The reviewed sources do not independently establish this award's denomination or cash settlement; payment date remains unknown.

Timeline

Published
2019-11-05explicit
Reported
2019-06-19explicit
Awarded
2019-06-26explicit
Fixed
2019-06-20explicit

Related visual models

Related cases

All 19 cases in Authorization and tenant boundaries

Sources

  1. Bypassing GitHub’s OAuth flowTeddy Katz · reviewed 2026-10-05
  2. Bug Bounty anniversary promotion: bigger bounties in January and FebruaryNeil Matatall · reviewed 2026-10-05

Record reviewed 2026-10-05. 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