cve.bz

CVE-2026-1999 github enterprise server: Incorrect Authorization

7.1 highEPSS 0.4%Fix available

High (7.1) in github enterprise server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
An incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed an attacker to merge their own pull request into a repository without having push access by exploiting an authorization bypass in the enable_auto_merge mutation for pull requests. This issue only affected repositories that allow forking as the attack relies on opening a pull request from an attacker-controlled fork into the target repository. Exploitation was only possible in specific scenarios. It required a clean pull request status and only applied to branches without branch protection rules enabled. This vulnerability affected GitHub Enterprise Server versions prior to 3.19.2, 3.18.5, and 3.17.11, and was fixed in versions 3.19.2, 3.18.5, and 3.17.11. This vulnerability was reported via the GitHub Bug Bounty program.

Severity

CVSS 4.0

7.1 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/SC:L/SI:H/SA:N

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-02-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • GitHub Enterprise Server: fixed in 3.17.11
  • GitHub Enterprise Server: fixed in 3.18.5
  • GitHub Enterprise Server: fixed in 3.19.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-1999 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-1999?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-1999?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-1999 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
GitHub Enterprise Serverfrom 3.17.0 before 3.17.11
GitHub Enterprise Serverfrom 3.18.0 before 3.18.5
GitHub Enterprise Serverfrom 3.19.0 before 3.19.2

Fixed in

ProductFixed in
GitHub Enterprise Server3.17.11
GitHub Enterprise Server3.18.5
GitHub Enterprise Server3.19.2

References

Check your stackJSON