Loading story…
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.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
6 events from the most recent confirmed update back to the earliest known activity.
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.
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.
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 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.
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.
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.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
11 references tracked. Mallory keeps watching after this page renders.
malware.news
Open sourcecyber.gc.ca
Open sourcecyber.gc.ca
Open sourcecybersecuritynews.com
Open sourcedocs.github.com
Open sourcedocs.github.com
Open sourcedocs.github.com
Open sourcedocs.github.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
GitHub disclosed and patched **CVE-2026-3854**, a critical command-injection flaw in its `git push` pipeline that allowed an authenticated user with repository push access to trigger remote code execution using a single crafted push. Wiz reported the bug on March 4, and GitHub said it reproduced the issue within about 40 minutes and deployed a fix to GitHub.com within roughly two hours, later publishing patches for supported GitHub Enterprise Server releases including **3.14.24, 3.15.19, 3.16.15, 3.17.12, 3.18.6, and 3.19.3**. The vulnerability stemmed from unsanitized user-supplied push option values being inserted into internal `X-Stat` headers, enabling attackers to inject trusted metadata, bypass sandboxing, and execute commands as the `git` service user. Researchers said the flaw could have led to **full server compromise** on GitHub Enterprise Server and, on GitHub.com, code execution on shared storage infrastructure where millions of repositories were accessible to the git service account, creating potential cross-tenant exposure. GitHub said forensic analysis and telemetry found **no evidence of malicious exploitation** and no indication that customer data was accessed, modified, or exfiltrated, but urged Enterprise Server administrators to upgrade immediately and review logs for suspicious push activity. Wiz described the bug as easy to exploit and highlighted its use of AI-assisted reverse engineering tools, including **IDA MCP**, to uncover the issue in GitHub’s closed-source components.
Jul 23, 2026
A vulnerability tracked as **`CVE-2024-0200`** allowed attackers with organization owner privileges to abuse an unsafe Ruby `Kernel#send()` call in GitHub’s organization repository settings flow and invoke unintended zero-argument methods on `Repository` objects. Researchers showed the bug could be used to trigger `Repository::GitDependency#nw_fsck()` and leak roughly **2 MB of environment variables** from a production GitHub.com container, exposing access keys, secrets, and internal configuration because spawned git processes inherited the parent environment. The issue affected **GitHub.com** and **GitHub Enterprise Server (GHES)** instances with GitHub Actions enabled, but the impact was more severe on GHES. STAR Labs reported that leaked variables on GHES could include `ENTERPRISE_SESSION_SECRET` and other Marshal-related secrets, which could be chained with forged Rails session cookies and an unsafe `Marshal.load` path to achieve **remote code execution**. GitHub hotfixed GitHub.com on December 26, 2023, and later released a patch and advisory, while recommended mitigations included allowlisting the `rid_key` parameter, reducing environment variables passed to git processes, rotating exposed secrets, and monitoring `repository_items` requests for abnormal `rid_key` values.
Jun 29, 2026
GitLab released security updates for Community Edition and Enterprise Edition in versions **16.6.1**, **16.5.3**, and **16.4.3**, urging affected self-managed installations to upgrade immediately. The fixes addressed multiple vulnerabilities spanning **XSS, privilege escalation, information disclosure, authorization bypass, package registry access issues, protected branch and pipeline schedule permission bypasses, and client-side denial of service**. The most severe issue was **`CVE-2023-6033`**, a high-severity cross-site scripting flaw in Jira integration configuration, while GitLab said **GitLab.com** was already running the patched version. One of the patched Enterprise Edition issues, **`CVE-2023-4658`**, was an incorrect authorization flaw that allowed a guest user to abuse the **"Allowed to merge"** permission when that right was inherited through a group. GitLab rated that bug **CVSS 3.1 / Low** and said it affected versions from **8.13 before 16.4.3**, **16.5 before 16.5.3**, and **16.6 before 16.6.1**. The release also included fixes for unauthorized access to release descriptions and other EE-specific authorization weaknesses, along with bundled component updates for **Mattermost**, **PostgreSQL**, and **pcre2**.
Jul 24, 2026