Skip to main content
VulnerabilityPublished

CVE-2026-15996: GitHub Enterprise Server · Uncontrolled Recursion

Affects GitHub Enterprise ServerSource CVE Database V5

0
Compare

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

Data as of 3 Nov 2026, 10:57 UTC

CVSS 4.0 base score
6.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.20.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 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 3 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubEnterprise ServerAffected
  • >=3.17.0 <3.17.16
  • >=3.18.0 <3.18.10
  • >=3.19.0 <3.19.7
  • >=3.20.0 <3.20.3
Fixed in–

AI-suggested

Upgrade GitHub Enterprise Server to one of the fixed versions: 3.20.3, 3.19.7, 3.18.10, or 3.17.16. These versions contain the official fix for this vulnerability. Patch status is confirmed by the vendor advisory information embedded in the description.

Description

CVE-2026-15996 is a denial of service vulnerability in GitHub Enterprise Server that allows unauthenticated attackers to cause excessive CPU usage and exhaust request-handling workers by sending crafted HTTP POST requests with deeply nested parameters. This affects all versions prior to 3.21 and was fixed in versions 3.20.3, 3.19.7, 3.18.10, and 3.17.16.

References

Community reviews

Loading reviews…