CVE-2026-3307: CWE-639 Authorization Bypass Through User-Controlled Key in GitHub Enterprise Server
CVE-2026-3307 is an authorization bypass vulnerability in GitHub Enterprise Server versions prior to 3. 21. It allows 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 owner_id parameter. The vulnerability does not permit adding arbitrary external users, only assigning existing trusted users as bypass reviewers. This issue was fixed in multiple patched versions starting from 3. 14. 25 and later. The CVSS 4. 0 score is 5. 3, indicating a medium severity level.
AI Analysis
Technical Summary
This vulnerability in GitHub Enterprise Server arises from improper authorization checks when modifying the secret scanning push protection delegated bypass reviewer list. Although authorization is verified against the repository in the URL, the action is applied to a different repository specified in the request body via the owner_id parameter. This allows an attacker with admin rights on one repository to assign existing trusted users as bypass reviewers on another repository without proper authorization. The vulnerability affects all versions prior to 3.21 and was addressed in patched releases including 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7, 3.19.4, and 3.20.1.
Potential Impact
An attacker with admin access on one repository can bypass authorization controls to modify the secret scanning push protection delegated bypass reviewer list on a different repository. The impact is limited to assigning existing trusted users as bypass reviewers and does not allow adding arbitrary external users. This could potentially weaken secret scanning protections on affected repositories.
Mitigation Recommendations
Fixes for this vulnerability have been released in GitHub Enterprise Server versions 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7, 3.19.4, and 3.20.1. Users should upgrade to one of these patched versions or later to remediate the issue. Since this is not a cloud service, remediation depends on applying these official patches. Patch status is confirmed by the vendor advisory embedded in the description.
CVE-2026-3307: CWE-639 Authorization Bypass Through User-Controlled Key in GitHub Enterprise Server
Description
CVE-2026-3307 is an authorization bypass vulnerability in GitHub Enterprise Server versions prior to 3. 21. It allows 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 owner_id parameter. The vulnerability does not permit adding arbitrary external users, only assigning existing trusted users as bypass reviewers. This issue was fixed in multiple patched versions starting from 3. 14. 25 and later. The CVSS 4. 0 score is 5. 3, indicating a medium severity level.
CVSS v4.0
Score 5.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in GitHub Enterprise Server arises from improper authorization checks when modifying the secret scanning push protection delegated bypass reviewer list. Although authorization is verified against the repository in the URL, the action is applied to a different repository specified in the request body via the owner_id parameter. This allows an attacker with admin rights on one repository to assign existing trusted users as bypass reviewers on another repository without proper authorization. The vulnerability affects all versions prior to 3.21 and was addressed in patched releases including 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7, 3.19.4, and 3.20.1.
Potential Impact
An attacker with admin access on one repository can bypass authorization controls to modify the secret scanning push protection delegated bypass reviewer list on a different repository. The impact is limited to assigning existing trusted users as bypass reviewers and does not allow adding arbitrary external users. This could potentially weaken secret scanning protections on affected repositories.
Mitigation Recommendations
Fixes for this vulnerability have been released in GitHub Enterprise Server versions 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7, 3.19.4, and 3.20.1. Users should upgrade to one of these patched versions or later to remediate the issue. Since this is not a cloud service, remediation depends on applying these official patches. Patch status is confirmed by the vendor advisory embedded in the description.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_P
- Date Reserved
- 2026-02-26T21:00:43.352Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e7faaa19fe3cd2cd00147c
Added to database: 4/21/2026, 10:31:06 PM
Last enriched: 4/29/2026, 11:11:56 AM
Last updated: 6/6/2026, 1:51:32 AM
Views: 59
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.