Loading story…
GitHub awarded researcher Saif Ghani a $100,000 bug bounty for reporting CVE-2026-3854, a critical remote-code-execution vulnerability in its Git push processing pipeline. The flaw reportedly enabled an unauthenticated attacker to supply a specially crafted repository URL during Git-related operations and execute arbitrary commands on GitHub backend infrastructure.
GitHub said it deployed mitigations shortly after receiving the report and completed a patch rollout through coordinated disclosure before detailed exploitation information became broadly available. Exploitation could have threatened public and private repository integrity, source-code confidentiality, Git objects, secrets and credentials, build workflows, and the wider software supply chain.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Saif Ghani announced that GitHub awarded him a $100,000 bug bounty for CVE-2026-3854. The reward was reported as GitHub's largest publicly disclosed Vulnerability Reward Program payout.
GitHub said it handled the vulnerability through coordinated disclosure, deployed mitigations shortly after receiving the report, and completed a patch rollout across affected services before detailed exploitation information became widely available.
Security researcher Saif Ghani (@sagitz_) disclosed CVE-2026-3854 to GitHub. The reported flaw affected GitHub's Git push processing pipeline and could allow unauthenticated command execution through a specially crafted repository URL.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
cyberaccord.com
Open sourcecryptika.com
Open sourcecybersecuritynews.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
GitHub has offered a **$100,000 bug bounty** for a **critical remote code execution (RCE)** vulnerability disclosed by security researcher `@sagitz_`. Public reporting indicates the company elevated the reward because of the severity of the issue, signaling that the flaw could have enabled highly impactful compromise if abused. Technical details, including an affected component, `CVE` identifier, and exploitation status, were not provided in the available reporting. Even so, the unusually large payout underscores the seriousness of the disclosed RCE and highlights GitHub's response through its vulnerability disclosure and bug bounty process.
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