Skip to main content

GitHub Enterprise Server EUVDEUVD-2026-53611

| CVE-2026-15996 MEDIUM
Uncontrolled Recursion (CWE-674)
2026-08-05 GitHub_P GHSA-3x3p-rpwc-h9wf
6.6
CVSS 4.0 · Vendor: GitHub_P
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify network-reachable GHES POST endpoint
  2. Delivery
    Craft form-encoded body with extreme parameter nesting depth
  3. Exploit
    Send unauthenticated HTTP POST request
  4. Execution
    Server recursively parses nested parameters pre-authentication
  5. Persist
    CPU exhaustion saturates worker process pool
  6. Impact
    Instance becomes unresponsive to all requests

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Recursion depth limits
Exploitation Conditions

No special conditions are required beyond network connectivity to the GitHub Enterprise Server instance. Because parameter parsing occurs before routing and authentication, no valid account, session token, or knowledge of specific endpoints is needed - any POST endpoint, including publicly accessible ones such as the login form, suffices. Exploitation is not limited to any specific configuration, feature flag, or non-default setting. What limits exploitation is network-level access: instances isolated behind a VPN or restricted to internal networks reduce the attacker pool to those with internal access. Additionally, the attack causes availability disruption only (no data exfiltration or integrity impact), and the effect is transient - the instance can recover once the malicious request volume stops and worker processes are recycled.

Impact

The CVSS 4.0 base score of 6.6 reflects a network-accessible (AV:N), low-complexity (AC:L), no-privileges-required (PR:N), no-user-interaction (UI:N) attack with high availability impact but zero confidentiality or integrity impact (VC:N/VI:N/VA:H). The E:U (unexploited) temporal modifier accurately signals no known active exploitation at time of scoring, and the vulnerability is absent from the CISA KEV catalog. No EPSS data was provided; however, given that the attack requires only a single unauthenticated HTTP request to any POST endpoint and completely disables the instance, real-world risk is materially higher than the base score suggests for organizations with internet-exposed GHES instances or adversaries with internal network access. The lack of authentication or configuration prerequisites means any network-reachable attacker can attempt this trivially, making patch urgency high for exposed instances despite the absence of confirmed exploitation.

Exploit ScenarioDerived

An unauthenticated attacker with network access to the GitHub Enterprise Server instance sends a single HTTP POST request to any endpoint (such as the login page or a public API route) with a form-encoded body containing parameters nested to an extreme depth, such as a[b][c][d]...[z]=1 repeated thousands of levels. The server's body parser recursively descends into the structure before any routing or authentication logic executes, consuming CPU until the process is blocked or killed, and repeating this at a modest request rate quickly saturates all available worker processes, rendering the instance unable to service legitimate requests.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 05, 2026

Denial of service in GitHub Enterprise Server allows unauthenticated remote attackers to render an instance fully unresponsive by submitting a crafted form-encoded HTTP POST request containing deeply nested parameters, triggering uncontrolled recursive parsing that exhausts both CPU and the pool of request-handling worker processes. Because parameter parsing occurs before routing and authentication checks, every POST endpoint on the instance serves as a viable attack surface, requiring no foothold or prior knowledge of application structure. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; the CVSS 4.0 E:U modifier confirms no known active exploitation at the time of scoring. GitHub has released patches across four supported release trains.

RemediationAI

The primary remediation is upgrading to one of the patched releases: 3.17.16, 3.18.10, 3.19.7, or 3.20.3, per GitHub's official release notes. Administrators should apply the patch corresponding to their current release train as soon as operationally feasible. For organizations that cannot immediately patch, compensating controls include deploying a reverse proxy or WAF in front of the GHES instance configured to enforce a maximum request body nesting depth or reject form-encoded payloads exceeding a defined parameter count threshold - though this may inadvertently block legitimate deep-nested form submissions and requires testing. Rate-limiting POST requests per source IP at the network perimeter can reduce the blast radius of an attack but will not prevent a determined attacker from sustaining the DoS from multiple sources. Restricting network-level access to the GHES instance to trusted IP ranges is the strongest compensating control where possible, since it eliminates unauthenticated remote attack surface entirely. No side effects are expected from upgrading within the same release train.

Affected VersionsENISA

Enterprise Server 3.19.0 ≤3.19.6
Enterprise Server 3.20.0 ≤3.20.2
Enterprise Server 3.17.0 ≤3.17.15
Enterprise Server 3.18.0 ≤3.18.9

Affected Packages

euvd enterprise_server no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-674 (Uncontrolled Recursion): the server's form-encoded body parser does not impose a depth limit on nested parameter structures, causing recursive descent into deeply nested parameter trees that consumes CPU proportional to nesting depth. Because HTTP body parsing in GitHub Enterprise Server is performed as a pre-routing middleware step - before authentication or route-specific logic - any valid POST endpoint can be used to trigger the condition without credentials. The affected product is identified via CPE cpe:2.3:a:github:enterprise_server:*:*:*:*:*:*:*:*, covering the self-hosted appliance distribution of GitHub's platform. The pattern is consistent with algorithmic complexity / ReDoS-class DoS issues where attacker-controlled input drives exponential or deeply recursive internal computation.

Know when Github gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_P) PRIMARY 6.6 MEDIUM
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
vuln.today AI 7.5 HIGH

Network-reachable with no authentication or configuration prerequisites; impact is purely availability (complete DoS), with no confidentiality or integrity effect.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_P).

CVSS VectorVendor: GitHub_P

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A denial of service vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to cause excessive CPU consumption and exhaust the pool of request-handling worker processes by sending a crafted form-encoded HTTP POST request containing deeply nested parameters. Because request parameters were parsed before routing and authentication, any POST endpoint could be used to trigger the condition, which could render the instance unresponsive. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.20.3, 3.19.7, 3.18.10, and 3.17.16.

Threat Intelligence Overview

EPSS Score
0.4%
Top 67% exploitable
Prevalence
Medium
self-hosted GitHub platform, widely used in enterprise DevOps
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

33
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +33
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

More in Github

View all
CVE-2026-1699 CRITICAL POC
10.0 Jan 30

Supply chain vulnerability in Eclipse Theia GitHub Actions workflow. The preview.yml workflow uses pull_request_target w

CVE-2026-27941 CRITICAL POC
9.9 Feb 26

Supply chain attack vector in OpenLIT GitHub Actions workflows. The pull_request_target trigger with checkout enables ma

CVE-2026-22869 CRITICAL POC
9.8 Jan 13

Eigent multi-agent workflow CI pipeline (ci.yml) uses pull_request_target with checkout of untrusted PR code, enabling a

CVE-2024-0200 CRITICAL POC
9.8 Jan 16

An unsafe reflection vulnerability was identified in GitHub Enterprise Server that could lead to reflection injection. R

CVE-2022-24724 CRITICAL POC
9.8 Mar 03

cmark-gfm is GitHub's extended version of the C reference implementation of CommonMark. Rated critical severity (CVSS 9.

CVE-2024-9487 CRITICAL POC
9.5 Oct 10

An improper verification of cryptographic signature vulnerability was identified in GitHub Enterprise Server that allowe

CVE-2026-28215 CRITICAL POC
9.1 Feb 26

Unauthenticated infrastructure overwrite in Hoppscotch API development ecosystem before 2026.2.0. Attackers can overwrit

CVE-2018-1000600 HIGH POC
8.8 Jun 26

A exposure of sensitive information vulnerability exists in Jenkins GitHub Plugin 1.29.1 and earlier in GitHubTokenCrede

CVE-2026-30920 HIGH POC
8.6 Mar 10

OneUptime versions prior to 10.0.19 allow unauthenticated attackers to hijack GitHub App integrations across projects by

CVE-2026-25221 HIGH POC
8.1 Feb 02

PolarLearn versions 0-PRERELEASE-15 and earlier lack proper state parameter validation in OAuth 2.0 authentication, enab

CVE-2026-23644 HIGH POC
7.5 Jan 18

Path traversal in esm.sh CDN prior to version 0.0.0-20260116051925-c62ab83c589e allows unauthenticated remote attackers

CVE-2024-42471 HIGH POC
7.5 Sep 02

actions/artifact is the GitHub ToolKit for developing GitHub Actions. Rated high severity (CVSS 7.5), this vulnerability

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy