Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

SSRF timing side-channel secret exfiltration in GitHub Enterprise Server notebook viewer

IdentifiersCVE-2026-5921CWE-918· Server-Side Request Forgery (SSRF)

CVE-2026-5921 is a server-side request forgery vulnerability in GitHub Enterprise Server (GHES) affecting versions prior to 3.21. In affected deployments, the notebook rendering/viewer service would follow HTTP redirects without revalidating the destination host when private mode was disabled. This allowed an unauthenticated attacker to abuse the notebook viewer as an SSRF primitive to reach internal services. The issue could then be chained with regex-based filter queries against an internal API and a timing side channel to infer sensitive environment variable values character by character. The attack relied on measuring response-time differences to determine whether guessed characters matched secret data. The vulnerability was fixed in GHES versions 3.14.26, 3.15.21, 3.16.17, 3.17.14, 3.18.8, 3.19.5, and 3.20.1.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation could allow an unauthenticated remote attacker to exfiltrate sensitive environment variables from the GHES instance via internal-service access and timing-based inference. Depending on what environment variables are present, this may expose secrets such as tokens, credentials, or configuration values, increasing the risk of further compromise of the appliance or connected internal services.

Mitigation

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

If immediate patching is not possible, reduce exposure by enabling private mode if operationally feasible, restricting unauthenticated access to notebook viewing/rendering functionality, and preventing the instance from reaching sensitive internal services via network segmentation or egress controls. Limit or eliminate open-redirect chaining paths, and review internal APIs that can be queried in ways that create measurable timing differences. Additional access controls around notebook services and internal endpoints can reduce exploitability until patching is completed.

Remediation

Patch, then assume compromise.

Upgrade GitHub Enterprise Server to a fixed release. The content states fixes are included in 3.14.26, 3.15.21, 3.16.17, 3.17.14, 3.18.8, 3.19.5, 3.20.1, and later supported versions prior to 3.21 should be brought to the corresponding patched build. Administrators should also review notebook rendering behavior and internal-service exposure as part of post-upgrade validation.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.