CVE-2026-9132: GitHub Enterprise Server Missing Authorization in Copilot Endpoint

Technical summary

CVE-2026-9132 is a missing authorization vulnerability (CWE-862) in the Copilot pull request description diff summary endpoint of GitHub Enterprise Server. The endpoint accepted cross-repository comparison ranges and rendered diffs without performing authorization checks on the target repository. This allowed an authenticated user with PR-comment privileges on at least one repository to construct API calls that would leak source code from any other repository on the instance, bypassing repository access controls. The vulnerability affected all versions prior to 3.21, with patches released for versions 3.17.17, 3.18.11, 3.19.8, and 3.20.4.

Business impact

This vulnerability poses a significant insider risk and intellectual property exposure concern. An employee or contractor with limited repository access could exfiltrate proprietary code, algorithms, or sensitive logic from restricted projects. For organizations using GitHub Enterprise Server to manage confidential codebases, this creates compliance violations (SOX, HIPAA, data residency laws) if sensitive code was accessed without authorization. The flaw is particularly concerning in multi-tenant or federated development environments where repository isolation is a key security boundary.

Affected systems

GitHub Enterprise Server versions prior to 3.21 are affected. Organizations running versions 3.17, 3.18, 3.19, or 3.20 should immediately upgrade to the patched releases: 3.17.17, 3.18.11, 3.19.8, or 3.20.4 respectively. Version 3.21 and later are not vulnerable. On-premises GitHub Enterprise Server instances are the only affected product line; GitHub.com SaaS is not impacted.

Exploitability

Exploitation requires a valid, authenticated account on the GitHub Enterprise Server instance with at least read access to one repository. This is a low barrier to entry—any legitimate user, contractor, or compromised credential can perform the attack. No special tools or complex steps are needed; the attacker simply structures a cross-repository comparison in the Copilot endpoint. The attack is also difficult to detect through normal audit logs, as it appears as legitimate API activity. The CVSS 3.1 score of 6.5 (Medium) reflects the requirement for authentication but acknowledges the high confidentiality impact.

Remediation

Immediately upgrade GitHub Enterprise Server to a patched version: 3.17.17, 3.18.11, 3.19.8, or 3.20.4. For instances on version 3.21 or later, no action is required. Administrators should verify their current version and plan upgrades according to your change management process. After patching, no configuration changes are necessary; the fix is automatic. Review audit logs for any suspicious cross-repository diff requests during the window the vulnerability was exposed.

Patch guidance

GitHub provides out-of-cycle security releases for this issue. Prioritize patching based on your instance version: (1) Identify your current GitHub Enterprise Server version via the Management Console or API; (2) consult the official GitHub advisory for your release line to confirm the patched version; (3) schedule downtime if required (verify whether the update requires a restart); (4) deploy the patch in a staging environment first to test Copilot and PR workflows; (5) roll out to production and verify the Copilot endpoint is functioning correctly post-deployment. Document the patch date for compliance records.

Detection guidance

Audit cross-repository API activity on your GitHub Enterprise Server logs, specifically requests to Copilot endpoints or diff summary features that reference repositories outside the user's normal access patterns. Look for authenticated users comparing code across repositories they don't typically interact with. Enable verbose logging if available. Check git access logs and API audit trails for anomalous repository access by users with limited repository permissions. Consider monitoring for unusual patterns of read activity on sensitive repositories by accounts that should not have such access. After patching, these patterns should cease if exploitation occurred.

Why prioritize this

This vulnerability ranks as a high-priority patch due to its insider-risk profile, low barrier to exploitation, and direct impact on code confidentiality. While authentication is required (limiting external attack), any internal user or compromised employee account can exploit it trivially. The impact on intellectual property and regulatory compliance is severe. Organizations with large, multi-team repositories or strict code compartmentalization should treat this as critical.

Risk score, explained

The CVSS 3.1 score of 6.5 (Medium) reflects: (1) Network-accessible endpoint (AV:N); (2) low attack complexity, requiring only valid credentials (AC:L, PR:L); (3) high confidentiality impact—source code from unauthorized repositories is leaked (C:H); (4) no integrity or availability impact (I:N, A:N); (5) unchanged security scope (S:U). The 'Medium' severity understates the business risk for organizations whose competitive advantage depends on code secrecy; security teams should treat this as a high-priority vulnerability in practice.

Frequently asked questions