Skip to main content
Mallory
← Back to News
zero-day-acquisitionstandards-framework-update

GitHub Offers $100,000 Bounty for Critical Remote Code Execution Flaw

Regulatory & Policy · 2 sources · Updated 4mo ago · First seen Jul 22, 2026

GitHub Offers $100,000 Bounty for Critical Remote Code Execution Flaw

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.

What this changes for youSee the reporting duties and controls this puts on the clock.
Get the context
Event timeline

How this story unfolded

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

1 event · Jul 22, 2026
  1. Jul 22, 20264mo ago

    GitHub issues $100,000 bounty for critical RCE vulnerability

    GitHub publicly issued a $100,000 bounty tied to a critical remote code execution vulnerability. The available references do not provide further technical details, a CVE, or exploitation information.

    GitHub issues $100,000 bounty for critical RCE vulnerability : r/netsec
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

Organizations

1 linked
GitHub
Do you run this?See what this changes for your reporting obligations and which controls it puts on the clock.
Get the Regulatory Context
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.