CVE 8.9 HIGH

Server-Side Request Forgery in GitHub Enterprise Server allowed extraction of sensitive environment variables via timing side-channel attack_CVE-2026-5921

8.9 / 10
HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L/E:P

Description

A server-side request forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed an attacker to extract sensitive environment variables from the instance through a timing side-channel attack against the notebook rendering service. When private mode was disabled, the notebook viewer followed HTTP redirects without revalidating the destination host, enabling an unauthenticated SSRF to internal services. By chaining this with regex filter queries against an internal API and measuring response time differences, an attacker could infer secret values character by character. Exploitation required that private mode be disabled and that the attacker be able to chain the instance's open redirect endpoint through an external redirect to reach internal services.Β This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.14.26, 3.15.21, 3.16.17, 3.17.14, 3.18.8, 3.19.5, and 3.20.1. This vulnerability was reported via the GitHub Bug Bounty program.

AI Analysis

Server-side request forgery vulnerability allowing extraction of sensitive environment variables via timing side-channel attack

Basic Information

ID CVE-2026-5921
Source GitHub_P
Published Apr 21, 2026 at 22:11

Affected Product

Vendor GitHub
Product Enterprise Server
Version 3.14.0
Affected Versions GitHub Enterprise Server 3.14.0
GitHub Enterprise Server 3.15.0
GitHub Enterprise Server 3.16.0
GitHub Enterprise Server 3.17.0
GitHub Enterprise Server 3.18.0
GitHub Enterprise Server 3.19.0
GitHub Enterprise Server 3.20.0

CWE Classification

AI Assessment

AI Score 8.9 / 10
AI Severity High
Vendor GitHub
Product GitHub Enterprise Server
Version 3.14.0, 3.15.0, 3.16.0, 3.17.0, 3.18.0, 3.19.0, 3.20.0

References

πŸ’­ Join the Security Discussion

πŸ”’ Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.