Live › vulnerability › CVE-2026-118237
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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 23:45 UTC. All times on this page are UTC.
Only GitHub Enterprise Server instances running releases before 3.23 are affected, and only through the Git service's SSH access. An attacker needs a user account with SSH access to the instance, so instances without SSH access for users are less exposed. Teams running GitHub.com or instances already on the fixed versions can skip it.
No product ranges from the sources yet.
ghe-version on the appliance3.233.22.3 on the 3.22 line3.21.8 on the 3.21 line3.20.10 on the 3.20 line3.19.14 on the 3.19 lineEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-118237")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.