CVE-2025-11578Network attack vector

Root SSH access via pre-receive symlink escape

Published Nov 10, 2025 · Updated Nov 10, 2025

Privilege escalation in GitHub Enterprise Server 3.14 through 3.18 allows remote authenticated users to gain root SSH access. Pre-receive hook cleanup follows attacker-created symlinks outside the hook environment and replaces system binaries, allowing a cleanup-time payload to install a root SSH key. Exploitation requires Enterprise administrator privileges and a crafted repository environment; successful exploitation gives persistent root-level appliance access.

CVSS severity7.5
High
EPSS probability0.66%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Privilege escalation in GitHub Enterprise Server 3.14 through 3.18 allows remote authenticated users to gain root SSH access. Pre-receive hook cleanup follows attacker-created symlinks outside the hook environment and replaces system binaries, allowing a cleanup-time payload to install a root SSH key. Exploitation requires Enterprise administrator privileges and a crafted repository environment; successful exploitation gives persistent root-level appliance access.

The record

CVE
CVE-2025-11578
Published
Nov 10, 2025
Updated
Nov 10, 2025
Vendor
Twitter
Product
GitHub Enterprise Server
Classifications
CWE-59, T1098.004
Attack vector
network
Privileges
admin

Timeline

How it unfolded

  1. Nov 10, 2025CVE publishedPublication date reported by the CVE source.
  2. Nov 10, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=3.14 <=3.14.18 changes=[{"at":"3.14.19","status":"unaffected"}]
  2. Affected versionversion=3.15 <=3.15.13 changes=[{"at":"3.15.14","status":"unaffected"}]
  3. Affected versionversion=3.16 <=3.16.9 changes=[{"at":"3.16.10","status":"unaffected"}]
  4. Affected versionversion=3.17 <=3.17.6 changes=[{"at":"3.17.7","status":"unaffected"}]
  5. Affected versionversion=3.18 <=3.18.0 changes=[{"at":"3.18.1","status":"unaffected"}]

What conditions does exploitation require?

Attack vectornetwork
Required privilegesadmin

What is affected?

Twitter · GitHub Enterprise Serverversion=3.14 <=3.14.18 changes=[{"at":"3.14.19","status":"unaffected"}]; version=3.15 <=3.15.13 changes=[{"at":"3.15.14","status":"unaffected"}]; version=3.16 <=3.16.9 changes=[{"at":"3.16.10","status":"unaffected"}]; version=3.17 <=3.17.6 changes=[{"at":"3.17.7","status":"unaffected"}]; version=3.18 <=3.18.0 changes=[{"at":"3.18.1","status":"unaffected"}]

Published CVSS scores

7.5GitHubCVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesadmin
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-59Improper Link Resolution Before File Access ('Link Following')
T1098.004SSH Authorized Keys

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo