9.2
Critique
CVE-2026-9312 A server-side request forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed an…
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.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| Enterprise Server 3.21 | 3.21.0 → < 3.21.1 | 3.21.1 |
| Enterprise Server 3.20 | 3.20.0 → 3.20.3 | Pas de correctif indiqué |
| Enterprise Server 3.19 | 3.19.0 → 3.19.7 | Pas de correctif indiqué |
| Enterprise Server 3.18 | 3.18.0 → 3.18.10 | Pas de correctif indiqué |
| Enterprise Server 3.17 | 3.17.0 → 3.17.16 | Pas de correctif indiqué |
| Enterprise Server 3.16 | 3.16.0 → 3.16.19 | Pas de correctif indiqué |
Autres CVE de Enterprise Server
Les 94 CVE de Enterprise Server →
CVE-2026-118237
Out-of-bounds read vulnerability in GitHub Enterprise Server allowed disclosure of process memory in the Git service
5.3
Moyenne
CVE-2026-110288
Cross-site request forgery vulnerability in GitHub Enterprise Server allowed deletion of stored ChatOps configuration through the Management Console
5.3
Moyenne
CVE-2026-104608
Use-after-free vulnerability in GitHub Enterprise Server allowed remote code execution in the Git service
7.7
Élevée
CVE-2026-96890
A Server-Side Request Forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed a…
8.7
Élevée