CVE-2026-18730 GitHub CVE debrief

Who should care

GitHub Enterprise Server administrators, security teams, and IT personnel responsible for managing and securing GitHub Enterprise Server instances should assess exposure and prioritize patching or mitigating vulnerable instances.

Why it matters

This SSRF vulnerability in GitHub Enterprise Server allows an unauthenticated attacker to send crafted outbound requests to an attacker-controlled host, potentially leading to unauthorized access or data breaches. GitHub Enterprise Server administrators should assess exposure and prioritize patching or mitigating vulnerable instances.

• Verify instance version and apply patches to prevent exploitation
• Monitor for suspicious outbound requests to detect potential attacks
• Assess exposure of GitHub Enterprise Server instances with internet-exposed management interfaces
• Prioritize patching or mitigating vulnerable instances to prevent unauthorized access

Technical summary

The vulnerability allows an unauthenticated attacker to send crafted outbound requests to an attacker-controlled host. An attacker positioned to intercept the outbound request could capture the HMAC token and replay it against privileged management agent endpoints. This SSRF vulnerability in GitHub Enterprise Server allows an unauthenticated attacker to send crafted outbound requests to an attacker-controlled host, potentially leading to unauthorized access or data breaches. High-availability deployments were not affected due to a topology restriction. This vulnerability affected GitHub Enterprise Server releases in the 3.17, 3.18, 3.19, 3.20, and 3.21 series and was fixed in versions 3.17.21, 3.18.15, 3.19.12,

Defensive priority

GitHub Enterprise Server administrators should assess exposure and prioritize patching or mitigating vulnerable instances, especially those with internet-exposed management interfaces.

Recommended defensive actions

• Assess exposure of GitHub Enterprise Server instances
• Prioritize patching or mitigating vulnerable instances
• Verify instance version and apply patches
• Monitor for suspicious outbound requests
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, affected versions, and fixed versions. GitHub Enterprise Server administrators can verify their instance's version and apply patches accordingly.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.