CVE-2026-3307: Authorization bypass in GitHub Enterprise Server secret scanning push protection allows cross-repository modification of delegated bypass reviewers
An authorization bypass vulnerability was identified in GitHub Enterprise Server that allowed an attacker with admin access on one repository to modify the secret scanning push protection delegated bypass reviewer list on another repository by manipulating the ownerid parameter in the request body. Authorization was verified against the repository in the URL, but the action was applied to a different repository specified in the request body. The impact is limited to assigning existing trusted users as bypass reviewers; it does not allow adding arbitrary external users. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7, 3.19.4 and 3.20.1. This vulnerability was reported via the GitHub Bug Bounty program.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-3307?
CVE-2026-3307 has been classified with a high severity due to its potential for unauthorized access and data modification.
How do I fix CVE-2026-3307?
To resolve CVE-2026-3307, upgrade your GitHub Enterprise Server to a version later than 3.21.
What does CVE-2026-3307 affect?
CVE-2026-3307 affects GitHub Enterprise Server versions prior to 3.21 and involves an authorization bypass in secret scanning push protection.
Who is impacted by CVE-2026-3307?
Any organization using GitHub Enterprise Server versions before 3.21 with delegated bypass reviewers could be impacted by CVE-2026-3307.
What is the nature of the vulnerability in CVE-2026-3307?
CVE-2026-3307 is an authorization bypass vulnerability that allows cross-repository modifications by unauthorized users.