Skip to main content
Mallory
← Back to News
standards-framework-update

GitHub Introduces Rate Limits for Private Vulnerability Reports

Regulatory & Policy · 3 sources · Updated 1mo ago · First seen Oct 8, 2026

GitHub Introduces Rate Limits for Private Vulnerability Reports

GitHub has introduced rate limits for private vulnerability reports, placing limits on submissions through its confidential security-reporting channel. The change was announced in GitHub’s changelog and subsequently covered by DevOps.com. Private vulnerability reporting allows researchers to notify maintainers of participating repositories about security flaws without exposing the findings through public issues, supporting coordinated disclosure and remediation.

The limits introduce a constraint that security researchers and repository maintainers need to account for in their disclosure workflows. Security teams should review GitHub’s updated reporting guidance, account for potential submission limits when conducting large-scale vulnerability research, and provide an alternative confidential reporting route in their security policies. The supplied references do not specify numerical thresholds, reset periods, or exceptions, so those operational details should be verified before changing reporting procedures.

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
  1. Reported Oct 2, 20262mo ago

    GitHub introduces rate limits for private vulnerability reports

    GitHub introduced rate limits for private vulnerability reports, as reported in its changelog and subsequent DevOps.com coverage. The supplied references do not specify the limits or when they were introduced.

    Rate limits for private vulnerability reports - GitHub Changelog
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.