# CVE-2026-3307: An authorization bypass vulnerability was identified in GitHub Enterprise Server that allowed an attacker with admin…

Source: https://junglewise.ai/threats/cve-2026-3307-an-authorization-bypass-vulnerability-was-identified-in-github  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-21  
License: CC BY 4.0 with a link back

CVE-2026-3307 · Severity: low · CVSS 2.7 · Published 2026-04-21

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 owner_id 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.

Technologies: [GitHub Enterprise Server](https://junglewise.ai/threats/technologies/github-enterprise-server). Vendors: [GitHub](https://junglewise.ai/threats/vendors/github).

## Quick answers

**Is CVE-2026-3307 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-3307 being exploited in the wild.

**How severe is CVE-2026-3307?** Low severity, with a CVSS score of 2.7, published 21 April 2026.

**Which products and versions are affected?** GitHub Enterprise Server. The advisory does not name versions.

**Is there a fix for CVE-2026-3307?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**Am I affected by CVE-2026-3307?** Check whether you run GitHub Enterprise Server. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Affected products

- GitHub Enterprise Server

## Related threats

- [GitHub Enterprise Server out-of-bounds read in SSH key negotiation](https://junglewise.ai/threats/cve-2026-118237-an-out-of-bounds-read-vulnerability-was-identified-in-github)
- [GitHub Enterprise Server CSRF in ChatOps integration removal](https://junglewise.ai/threats/cve-2026-110288-a-cross-site-request-forgery-vulnerability-was-identified-in)
- [GitHub Enterprise Server use-after-free in Git service babeld](https://junglewise.ai/threats/cve-2026-104608-a-remote-code-execution-vulnerability-was-identified-in-github)
- [GitHub Enterprise Server SSRF in secret scanning validator](https://junglewise.ai/threats/cve-2026-96890-a-server-side-request-forgery-ssrf-vulnerability-was-identified)
- [GitHub Enterprise Server missing authorization in GraphQL API](https://junglewise.ai/threats/cve-2026-103620-a-missing-authorization-vulnerability-was-identified-in-github)