CVE-2026-18730Network attack vector

Management token exposure via unauthenticated SSRF

Published Sep 1, 2026 · Updated Sep 2, 2026

SSRF in vulnerable GitHub Enterprise Server releases allows remote attackers to expose a management token through the Manage API. An unauthenticated endpoint parses attacker-supplied cluster configuration and signs only a timestamp, leaving the request path and body outside the gateway-to-agent HMAC. Exploitation requires interception of the outbound request and a standalone topology; the captured token can be replayed against privileged management agent endpoints, while high-availability deployments are unaffected.

CVSS severity8.2
High
EPSS probability0.29%
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

SSRF in vulnerable GitHub Enterprise Server releases allows remote attackers to expose a management token through the Manage API. An unauthenticated endpoint parses attacker-supplied cluster configuration and signs only a timestamp, leaving the request path and body outside the gateway-to-agent HMAC. Exploitation requires interception of the outbound request and a standalone topology; the captured token can be replayed against privileged management agent endpoints, while high-availability deployments are unaffected.

The record

CVE
CVE-2026-18730
Published
Sep 1, 2026
Updated
Sep 2, 2026
Vendor
Twitter
Product
GitHub Enterprise Server
Classifications
CWE-918, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 1, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 2, 2026Record 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.17.0 <=3.17.18 changes=[{"at":"3.17.19","status":"unaffected"}]
  2. Affected versionversion=3.18.0 <=3.18.12 changes=[{"at":"3.18.13","status":"unaffected"}]
  3. Affected versionversion=3.19.0 <=3.19.9 changes=[{"at":"3.19.10","status":"unaffected"}]
  4. Affected versionversion=3.20.0 <=3.20.5 changes=[{"at":"3.20.6","status":"unaffected"}]
  5. Affected versionversion=3.21.0 <=3.21.3 changes=[{"at":"3.21.4","status":"unaffected"}]

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Twitter · GitHub Enterprise Serverversion=3.17.0 <=3.17.18 changes=[{"at":"3.17.19","status":"unaffected"}]; version=3.18.0 <=3.18.12 changes=[{"at":"3.18.13","status":"unaffected"}]; version=3.19.0 <=3.19.9 changes=[{"at":"3.19.10","status":"unaffected"}]; version=3.20.0 <=3.20.5 changes=[{"at":"3.20.6","status":"unaffected"}]; version=3.21.0 <=3.21.3 changes=[{"at":"3.21.4","status":"unaffected"}]

Published CVSS scores

8.2GitHub Advisory DatabaseCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

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
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
T1190Exploit Public-Facing Application

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