Skip to main content
Mallory
CriticalVulnerability

CVE-2026-9312: Pre-authentication SSRF in GitHub Enterprise Server upload endpoint

Published May 27, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.2Critical · v4
EPSS9.2%95th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
GitHub
IdentifiersCVE-2026-9312CWE-918 · Server-Side Request Forgery (SSRF)

CVE-2026-9312 is a critical server-side request forgery vulnerability in GitHub Enterprise Server affecting versions prior to 3.22, including fixed patch lines before 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.2. The flaw exists in an upload endpoint where insufficient input validation on request parameters allowed an unauthenticated attacker to inject path traversal content and alter the intended request flow. By doing so, the attacker could cause the server to issue crafted requests to internal services and redirect internal API calls to unintended destinations. The issue is pre-authentication and network-reachable, making it exploitable without a valid account when the affected service is accessible.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can let an unauthenticated attacker use the GitHub Enterprise Server instance as a proxy to reach internal services that are not directly exposed. This can result in unauthorized access to internal APIs and disclosure of sensitive information, including credentials or configuration data available to those internal services. Depending on the environment, the vulnerability could expand an attacker’s visibility into internal infrastructure and weaken trust boundaries between the appliance and backend services.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of the affected GitHub Enterprise Server instance to untrusted networks, restrict access to the vulnerable upload functionality as much as operationally feasible, and enforce network segmentation so the appliance cannot freely reach sensitive internal services. Limit outbound connectivity from the appliance to only required destinations, monitor for anomalous server-originated requests to internal systems, and review internal services for credential exposure paths reachable from the appliance. These measures reduce exploitability but do not eliminate the underlying flaw.

Remediation

Patch, then assume compromise.

Upgrade GitHub Enterprise Server to a fixed release. Reported fixed versions include 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.2, with later supported releases such as 3.22 and above also not affected. If operating on an older supported branch, apply the vendor patch level for that branch immediately. After upgrading, verify that the appliance is running the corrected release and that any required package-signing key rotation or upgrade prerequisites published for the relevant release train have been completed.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GitHubEnterprise Serverapplication
FAQ

Frequently asked questions

Is CVE-2026-9312 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-9312 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-9312?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-9312.
Is there a patch for CVE-2026-9312?
Upgrade GitHub Enterprise Server to a fixed release. Reported fixed versions include 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.2, with later supported releases such as 3.22 and above also not affected.
What products are affected by CVE-2026-9312?
GitHub Enterprise Server.
How severe is CVE-2026-9312?
CVE-2026-9312 has a CVSS v4 score of 9.2 (Critical) and an EPSS score of 9.2% (95th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.