---
id: "CVE-2026-118237"
kind: "vulnerability"
aliases: ["CVE-2026-118237"]
title: "GitHub Enterprise Server: SSH re-key flaw leaks adjacent process memory"
severity: "medium"
cvss: 5.3
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["git", "github-enterprise-server", "runtime", "self-hosted", "ssh"]
not_affected_if: ["fixed-version", "github-com", "no-ssh-access"]
published_at: "2026-11-03T23:17:33+00:00"
first_seen_at: "2026-11-03T23:45:14+00:00"
updated_at: "2026-11-03T23:45:47+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-118237", "first_seen_at": "2026-11-03T23:45:14+00:00"}]
---

# GitHub Enterprise Server: SSH re-key flaw leaks adjacent process memory

GitHub Enterprise Server's Git service (babeld) sized the SSH session identifier with the wrong digest length during host key proof, an out-of-bounds read. An authenticated user can re-key to an algorithm with a longer hash and get adjacent process memory signed and returned, where some of it may be recoverable.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed GitHub Enterprise Server version in the admin console or with `ghe-version` on the appliance
- Confirm whether the instance is running a release prior to `3.23`

## Fix

- Upgrade to `3.22.3` on the 3.22 line
- Upgrade to `3.21.8` on the 3.21 line
- Upgrade to `3.20.10` on the 3.20 line
- Upgrade to `3.19.14` on the 3.19 line

## Timeline

- 2026-11-03T23:45:14+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-118237

## From the sources

An out-of-bounds read vulnerability was identified in GitHub Enterprise Server in the Git service (babeld). When proving possession of a host key, babeld's SSH implementation sized the session identifier by the current digest length rather than its own. An attacker with an account and SSH access could re-key to an algorithm with a longer hash, causing adjacent process memory to be signed and returned to the client, where a limited amount of it may be recoverable. This vulnerability affected all releases prior to 3.23 and was fixed in versions 3.22.3, 3.21.8, 3.20.10, and 3.19.14. This vulnerability was reported via the GitHub Bug Bounty program.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_