GitHub Introduces Rate Limits for Private Vulnerability Reports
Regulatory & Policy · 3 sources · Updated 1mo ago · First seen Oct 8, 2026

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.


