CVE-2026-116643

8.6High

Published 18 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

8.6CVSS

High

0CVSS v4.010

Attack vector
Network
Complexity
Low
Privileges
Low
User action
None
Impact
High impact on confidentiality, integrity
Weakness
CWE-289

What an attacker gets

Authenticated organization members can read and modify private repositories belonging to other users. This requires an attacker to already possess a valid SSH certificate issued by the instance's trusted certificate authority.

Root cause

The SSH certificate authentication mechanism fails to properly validate the scope of the provided certificate.

Affected versions

GitHub Enterprise Server releases prior to 3.23.

CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Fix & remediation

Upgrade to GitHub Enterprise Server version 3.19.16, 3.20.12, 3.21.10, or 3.22.5. If immediate patching is not possible, restrict SSH certificate authority access.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

An SSH certificate authentication bypass vulnerability in GitHub Enterprise Server allowed an authenticated organization member to read and modify another user's private repositories within the trusted certificate authority's scope. Exploitation required an instance using built-in authentication and a valid certificate issued to the attacker by a trusted SSH certificate authority. This vulnerability affected supported GitHub Enterprise Server releases prior to 3.23 and was fixed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5. This vulnerability was reported via the GitHub Bug Bounty program.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-116643