Skip to main content
VulnerabilityPublished

CVE-2026-103620: GitHub Enterprise Server · Missing Authorization

Affects GitHub Enterprise ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium · fixed in 3.22.2 : update GitHub Enterprise Server when convenient.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.22.2, 3.21.7, 3.20.9 +2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
GitHubEnterprise ServerAffected
  • >=3.22.0 <3.22.2
Fixed in
  • 3.22.2
GitHubEnterprise ServerAffected
  • >=3.21.0 <3.21.7
Fixed in
  • 3.21.7
GitHubEnterprise ServerAffected
  • >=3.20.0 <3.20.9
Fixed in
  • 3.20.9
GitHubEnterprise ServerAffected
  • >=3.19.0 <3.19.13
Fixed in
  • 3.19.13
GitHubEnterprise ServerAffected
  • >=3.18.0 <3.18.16
Fixed in
  • 3.18.16

AI-suggested

The vulnerability has been fixed in GitHub Enterprise Server versions 3.18.16, 3.19.13, 3.20.9, 3.21.7, and 3.22.2. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.

Description

A missing authorization vulnerability was identified in GitHub Enterprise Server that allowed a repository collaborator with write access to delete the current default branch through the GraphQL API and cause an attacker-controlled branch to become the new default. In repositories that required pull-request review but did not restrict branch deletion, this bypassed the review requirement and caused fresh clones and default-branch API requests to use attacker-controlled content. This vulnerability affected supported GitHub Enterprise Server releases in the 3.18, 3.19, 3.20, 3.21, and 3.22 series and was fixed in versions 3.18.16, 3.19.13, 3.20.9, 3.21.7, and 3.22.2. This vulnerability was reported via the GitHub Bug Bounty program.

References

Community reviews

Loading reviews…