CVE-2026-18730 GitHub CVE debrief

Who should care

Administrators of GitHub Enterprise Server instances should apply patches to prevent potential SSRF attacks. This includes reviewing current deployments for affected versions and ensuring that patches are applied promptly. Security teams should also monitor for suspicious outbound requests that could indicate exploitation attempts. Additionally, operators of high-availability deployments should verify their configurations to ensure they are not vulnerable despite the topology restriction. Vulnerability management teams should prioritize patching based on the severity of the vulnerability and the potential impact on their systems. Platform administrators should also review compensating controls for exposed systems while remediation is scheduled and verified. Asset inventory management should be updated to reflect the affected systems and track exceptions during remediation efforts. Rollback and change window planning should consider the potential downtime or impact on services during patch application. Source tracking and monitoring should be implemented to detect potential exploitation attempts and verify the effectiveness of patches and mitigations. This vulnerability affects all versions of GitHub Enterprise Server prior to 3.22, so a thorough review of current versions and configurations is necessary to ensure protection against potential attacks. The vulnerability allows attackers to capture authentication tokens and replay them against privileged management agent endpoints, which could lead to unauthorized access or control of the affected systems. Therefore, it is crucial for organizations to assess their exposure and apply necessary patches or mitigations promptly to prevent potential exploitation. The GitHub Bug Bounty program reported this vulnerability, and defenders should review the official advisory for detailed information on affected versions and patches. To prevent potential SSRF attacks, organizations should also restrict access to Manage API endpoints and implement monitoring for suspicious outbound requests. By taking these steps, organizations can reduce the risk associated with this vulnerability and protect their GitHub Enterprise Server 3.

Technical summary

A server-side request forgery (SSRF) vulnerability was identified in GitHub Enterprise Server, allowing unauthenticated attackers to send crafted outbound requests. The vulnerability was fixed in multiple versions, including 3.17.19 and 3.21.4. An unauthenticated endpoint parsed an attacker-supplied cluster configuration and issued gateway-to-agent requests whose HMAC authenticated only a timestamp, not the request path or body.

Defensive priority

Organizations using GitHub Enterprise Server should prioritize patching to prevent potential SSRF attacks.

Recommended defensive actions

• Apply patches from GitHub Enterprise Server versions 3.17.19, 3.18.13, 3.19.10, 3.20.6, or 3.21.4.
• Restrict access to Manage API endpoints.
• 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.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The vulnerability was reported via the GitHub Bug Bounty program. GitHub Enterprise Server versions prior to 3.22 are affected, with fixes available in versions 3.17.19, 3.18.13, 3.19.10, 3.20.6, and 3.21.4. To verify, defenders should review the official advisory and assess their deployment configurations. High-availability deployments were not affected due to a topology restriction.

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.