Skip to main content

Description

An improper neutralization of special elements vulnerability was identified in GitHub Enterprise Server that allowed an attacker with push access to a repository to achieve remote code execution on the instance. During a git push operation, user-supplied push option values were not properly sanitized before being included in internal service headers. Because the internal header format used a delimiter character that could also appear in user input, an attacker could inject additional metadata fields through crafted push option values. This vulnerability was reported via the GitHub Bug Bounty program and has been fixed in GitHub Enterprise Server versions 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7 and 3.19.4.

Key Findings

as of 2026-11-22
All KEV statistics→
  • Its current EPSS score (41.9%) is higher than that of 45% of CISA KEV entries.

Severity

CVSS 4.0 · CNA · CVSS-B8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NOpen in CVSS calculator
SSVC · CISA-ADP
Exploitationnone
Automatableno
Technical impacttotal

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
14 days
Asset not publicly exposed
Next upgrade
fix on system upgrade

If CISA adds it to the KEV catalog: 3 days and forensic triage on a publicly exposed asset, 14 days on other assets.

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (not listed) and CISA's SSVC values (automatable no, technical impact total, 2026-04-28).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised. Fix on system upgrade means remediating the next time the asset receives a scheduled major upgrade or rebuild.

If CISA adds the CVE to the KEV catalog, the timeline shortens.

Affected Products

ProductAffected versions
GitHub
Enterprise Server
3.14.0 to 3.14.24 (fixed ≥ 3.14.25)
3.15.0 to 3.15.19 (fixed ≥ 3.15.20)
3.16.0 to 3.16.15 (fixed ≥ 3.16.16)
3.17.0 to 3.17.12 (fixed ≥ 3.17.13)
3.18.0 to 3.18.6 (fixed ≥ 3.18.7)
3.19.0 to 3.19.3 (fixed ≥ 3.19.4)

More from GitHub

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.