Skip to main content
No exploitation reportedFix available

CVE-2026-9312

No exploitation reported by the sources we read.

  • Published2026-05-27
  • Fixed in3.20.3 · 3.19.7 · 3.18.10 · 3.17.16 · 3.16.19
  • WeaknessCWE-918

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A server-side request forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to send crafted requests to internal services by exploiting insufficient input validation in an upload endpoint. By injecting path traversal content into request parameters, an attacker could bypass the intended request flow and redirect internal API calls, potentially accessing internal services and exposing sensitive credentials. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.2. This vulnerability was reported via the GitHub Bug Bounty program.

Timeline

dates in UTC
  1. 2026-05-2700:16CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-25 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-9312?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-9312?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Github enterprise server
BranchAffectedFixed in
3.20≥ 3.20.0, < 3.20.33.20.3
3.19≥ 3.19.0, < 3.19.73.19.7
3.18≥ 3.18.0, < 3.18.103.18.10
3.17≥ 3.17.0, < 3.17.163.17.16
3.16≥ 3.16.0, < 3.16.193.16.19
3.21= 3.21.1no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Github enterprise server to 3.20.3 · 3.19.7 · 3.18.10 · 3.17.16 · 3.16.19

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2026-05-27
  • OpenCVESSVC decisionnone—
  • CNACVSS 4.09.2read 2026-10-23
  • NVDCVSS 3.18.2read 2026-10-23
  • CNAweakness (CWE)CWE-918read 2026-10-23
  • FIRST EPSSEPSS score9.2 %2026-10-25

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-05-27
Last Modified
2026-07-23
NVD status
Modified

Frequently asked questions

What is CVE-2026-9312?

A server-side request forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to send crafted requests to internal services by exploiting insufficient input validation in an upload endpoint. By injecting path traversal content into request parameters, an attacker could bypass the intended request flow and redirect internal API calls, potentially accessing internal services and exposing sensitive credentials. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.2. This vulnerability was reported via the GitHub Bug Bounty program.

Is CVE-2026-9312 actively exploited?

Active exploitation of CVE-2026-9312 has not been confirmed. Its EPSS score was 9.2% on 2026-10-25, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-9312?

CVE-2026-9312 has a CVSS v3 base score of 8.2 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month