Skip to main content
Mallory
← Back to News
widely-deployed-product-advisoryinternet-facing-service-vulnerabilityprivilege-escalation-techniqueidentity-authentication-vulnerability

GitHub Enterprise Server patches critical SSRF and Dirty Frag privilege escalation flaws

Patch & Detection Intelligence · 11 sources · Updated 4mo ago · First seen May 27, 2026

GitHub Enterprise Server patches critical SSRF and Dirty Frag privilege escalation flaws

GitHub released urgent security updates for GitHub Enterprise Server to fix multiple severe vulnerabilities affecting versions 3.16 through 3.20, led by CVE-2026-9312, a critical pre-authentication SSRF flaw in an upload endpoint. The bug allowed unauthenticated attackers to craft requests with path traversal content and force the appliance to make internal HTTP requests, potentially exposing internal services, credentials, and configuration data. GitHub said the issue was reported through its bug bounty program and remediated in 3.16.20, 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.1.

The updates also address the high-severity Linux kernel local privilege-escalation flaws CVE-2026-43284 and CVE-2026-43500, known as Dirty Frag, which could let a local user gain root on vulnerable appliances. Additional fixes and hardening cover a timing side-channel issue and another SSRF-related weakness tied to package and notebook-related functionality, including environments with GitHub Packages enabled or private mode disabled. GitHub revoked the signing key for GHES release packages and instructed administrators to rotate trusted local GPG public keys before installing the patched releases, urging rapid upgrades for internet-facing and shared multi-tenant deployments.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

6 events · Mar 10, 2026 – Jul 16, 2026
  1. Jul 16, 20264mo ago

    GitHub publishes new GHES security bulletin with updated patched versions

    GitHub published security bulletins on 2026-07-16 addressing vulnerabilities in GitHub Enterprise Server. The bulletin lists affected release trains as 3.21.x before 3.21.3, 3.20.x before 3.20.5, 3.19.x before 3.19.9, 3.18.x before 3.18.12, and 3.17.x before 3.17.18, and advises administrators to apply the updates.

    Bulletin de sécurité GitHub (AV26-720) - Malware News - Malware Analysis, News and Indicators
  2. May 27, 20266mo ago

    GitHub removes vulnerable package endpoint to mitigate timing leak

    GitHub mitigated the timing side-channel issue affecting the security advisories package lookup feature by removing the vulnerable package endpoint. The flaw could leak sensitive environment variables on servers with GitHub Packages enabled.

    GitHub Enterprise Server Vulnerabilities Patched • Daily CyberSecurity
  3. May 27, 20266mo ago

    GitHub revokes GHES package signing key and requires key rotation

    Alongside the GHES security updates, GitHub revoked the signing key used for GHES release packages and instructed administrators to rotate trusted local GPG public keys before validating or installing patched releases. The requirement was presented as part of the remediation guidance for affected deployments.

    GitHub Enterprise Server 3.20.3 Released With Fox for Critical Vulnerabilities
  4. May 27, 20266mo ago

    GitHub releases GHES security updates for multiple severe flaws

    GitHub released security updates for GitHub Enterprise Server to fix multiple vulnerabilities affecting versions 3.16 through 3.20, including the critical pre-authentication SSRF flaw CVE-2026-9312 and the Dirty Frag local privilege-escalation issues. Patched versions cited include 3.16.20, 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.1, while one report also highlights release 3.20.3 as a security-focused patch.

    GitHub Enterprise Server 3.20.3 Released With Fox for Critical Vulnerabilities
  5. May 27, 20266mo ago

    GitHub Bug Bounty report identifies CVE-2026-9312 in GHES

    The SSRF vulnerability CVE-2026-9312 in GitHub Enterprise Server was reported through the GitHub Bug Bounty program. The flaw allowed an unauthenticated attacker to send crafted requests to internal services via an upload endpoint.

    CVE-2026-9312 - Server-Side Request Forgery vulnerability in GitHub Enterprise Server allowed access to internal services via path traversal in upload endpoint
  6. Mar 10, 20268mo ago

    GitHub ships GHES 3.21.2 and 3.21.3 with additional security fixes

    GitHub released GHES 3.21.2 and 3.21.3 to remediate multiple vulnerabilities beyond the earlier CVE-2026-9312 fix, including CVE-2026-15343 in the Dependabot updater container and several medium-severity issues affecting repository access, token permissions, OAuth scope exposure, and denial of service. The release notes also note a dnsmasq update addressing six CVEs.

    Release notes - GitHub Enterprise Server 3.21 Docs
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Github Enterprise Server
Do you run this?See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
Prioritize This Patch
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.