Security readout for executives and security teams
Plain-English summary
GitHub Enterprise Server had a critical flaw that could let an unauthenticated attacker make the server contact internal services. If abused, this could expose sensitive credentials or affect internal systems reachable from the GHES appliance.
Executive priority
Handle as urgent for any self-hosted GHES deployment. The issue is critical because unauthenticated attackers may pivot through a trusted source-code platform toward internal services, but public exploitation evidence is not provided in the source bundle.
Technical view
CVE-2026-9312 is a CWE-918 SSRF in GitHub Enterprise Server caused by insufficient validation in an upload endpoint. The source says path traversal content in request parameters could redirect internal API calls. It affects GHES versions before 3.22 and is fixed in listed maintenance releases.
Likely exposure
Organizations running self-hosted GitHub Enterprise Server 3.16 through vulnerable 3.21 maintenance levels are the exposed population. GitHub.com is not identified as affected in the provided sources. Exposure is highest where GHES can reach sensitive internal services or metadata endpoints.
Exploitation context
The CVE record describes unauthenticated network exploitation, but with high attack complexity and prerequisite attack conditions. The source bundle does not show CISA KEV listing or other evidence of active exploitation. It was reported through GitHub's Bug Bounty program.
Researcher notes
Evidence is limited to the CVE description and GitHub release-note references. The description identifies SSRF via path traversal content in upload request parameters, but does not name the exact endpoint or provide proof-of-concept details. Avoid assuming exploit availability or compromise without local telemetry.
Mitigation direction
- Upgrade GHES to 3.17.17, 3.18.11, 3.19.8, 3.20.4, 3.21.2, or later supported guidance.
- Prioritize internet-facing or broadly reachable GHES appliances first.
- Restrict GHES outbound access to only required internal services where operationally feasible.
- Review GitHub release notes for any branch-specific upgrade prerequisites.
- Monitor GitHub advisories and release notes for follow-up guidance.
Validation and detection
- Inventory all GitHub Enterprise Server appliances and record exact versions.
- Treat any GHES version before the listed fixed maintenance releases as vulnerable.
- Confirm upgrade completion from the GHES admin interface or approved asset inventory.
- Review logs for unusual upload endpoint activity and unexpected internal service requests.
- Check whether GHES has network reachability to sensitive internal services or credential endpoints.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-9312 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.2 (4.0)
- Known Exploited
- No
- Published
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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——GitHub_PVulnerability scoring details
Base CVSS 4.0 score
9.2CriticalVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://docs.github.com/en/enterprise-server@3.17/admin/release-notes#3.17.17CVE reference, GitHub_P · release-notes
- https://docs.github.com/en/enterprise-server@3.18/admin/release-notes#3.18.11CVE reference, GitHub_P · release-notes
- https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.8CVE reference, GitHub_P · release-notes
- https://docs.github.com/en/enterprise-server@3.20/admin/release-notes#3.20.4CVE reference, GitHub_P · release-notes
- https://docs.github.com/en/enterprise-server@3.21/admin/release-notes#3.21.2CVE reference, GitHub_P · release-notes
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.