CVSS 4.0
7.7 highCVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:N/SA:NCVE-2026-104608
High (7.7) in github enterprise server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
A remote code execution vulnerability was identified in GitHub Enterprise Server in the Git service (babeld). babeld held references into internal collections while calling into the SSH library, where a re-entrant callback could modify a collection and invalidate those references. An attacker with an account and SSH access to the instance could leverage this use-after-free into a controlled write and run arbitrary commands as babeld, including disclosure of its environment secrets. Exploitation required per-build memory offsets; failed attempts crashed babeld. This affected all releases prior to 3.23 and was fixed in 3.22.3, 3.21.8, 3.20.10, and 3.19.14. This vulnerability was reported via the GitHub Bug Bounty program.
Severity
- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWEs
- CWE-416 Use After Free
CWE-1265 Unintended Reentrant Invocation of Non-reentrant Code Via Nested Calls - Published
- Modified
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-104608 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-104608?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-104608?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-104608 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
- github:enterprise server
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| GitHub Enterprise Server | from 3.19.0 before 3.19.* |
| GitHub Enterprise Server | from 3.20.0 before 3.20.* |
| GitHub Enterprise Server | from 3.21.0 before 3.21.* |
| GitHub Enterprise Server | from 3.22.0 before 3.22.* |
Fixed in
| Product | Fixed in |
|---|---|
| GitHub Enterprise Server | 3.19.14 |
| GitHub Enterprise Server | 3.20.10 |
| GitHub Enterprise Server | 3.21.8 |
| GitHub Enterprise Server | 3.22.3 |
Attack patterns (CAPEC)
- CAPEC-74 Manipulating State Likelihood: Medium · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
References
- https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.14
- https://docs.github.com/en/enterprise-server@3.20/admin/release-notes#3.20.10
- https://docs.github.com/en/enterprise-server@3.21/admin/release-notes#3.21.8
- https://docs.github.com/en/enterprise-server@3.22/admin/release-notes#3.22.3