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

GitHub · Authorization and tenant boundaries

GitHub comparison output lacked source-repository authorization

GitHub Enterprise Server's comparison feature could reveal limited code from a repository the user was not allowed to read. The user needed existing repository access and prior knowledge of private-repository references; the report does not establish unrestricted repository access. GitHub awarded USD 10,000 for the finding.

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

Root cause

GitHub identifies an access-control failure in cross-repository comparison (vendor-report; vendor-release). Permission to read one repository did not grant permission to see code from another repository in the comparison. The user needed existing repository access and prior knowledge of private-repository references; this was not unrestricted anonymous browsing. The general lesson is to check access to every source used in a combined view. The vendor does not disclose how the access checks were implemented.

Demonstrated impact

The vendor confirms limited code disclosure from an otherwise unauthorized repository (vendor-report; vendor-release). The public summary does not establish complete repository extraction, write access, account takeover, or exploitation in the wild; those outcomes must not be inferred from the broader report title.

What to check for

  • Editorial design lesson: authorize every contributing source under the requesting actor before returning a combined or derived view.
  • Editorial review objective: ensure that permission to access one repository never substitutes for permission to read another repository’s content.
  • GitHub lists historical fixes in GHES 3.14.17, 3.15.12, 3.16.8 and 3.17.5 (vendor-report). These are historical remediation evidence, not current upgrade recommendations; the 3.17 documentation now marks that release series unsupported (vendor-release).

Award and evidence

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

One report award; cash receipt is unverified. USD is inferred from HackerOne’s platform-wide payment policy reviewed in October 2026, later than the August 2025 award; that context does not independently establish settlement.

  • Public report content supplies a vendor summary, not implementation-level patch details or a complete demonstration transcript.
  • GitHub.com deployment timing and exploitation-in-the-wild status are not established by the reviewed sources.
  • Release availability, report resolution and detailed publication have different dates.
  • Cash receipt is unverified; later platform-wide USD policy is contextual denomination evidence.

Timeline

Published
2025-09-23explicit · Detailed report disclosure event, activity-37054322.
Public Disclosure
2025-08-25explicit · Vendor advisory in Enterprise Server 3.17.5 release notes preceded the detailed report.
Reported
2025-05-03explicit
Awarded
2025-08-26explicit
Fixed
2025-08-25explicit · Public GHES 3.17.5 release. Report Resolved status is August 26; GitHub.com deployment timing is not established.

Related visual models

Related cases

All 19 cases in Authorization and tenant boundaries

Sources

  1. GitHub HackerOne report 3124517GitHub security team and furbreeze · reviewed 2026-10-03
  2. GitHub Enterprise Server 3.17.5 release notesGitHub · reviewed 2026-10-03
  3. Vulnerability Disclosure Standards: Bug Bounty payment denominationHackerOne · reviewed 2026-10-03

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