<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Google Pauses OSS Product Bug Bounty Rewards After Surge in Invalid Automated Reports]]></title><description><![CDATA[<p dir="auto">Google has paused product vulnerability reports through its bug bounty program for open-source software, effective <strong>October 1</strong>. Researchers can no longer submit security flaws found in the code of projects such as <strong>Go</strong>, <strong>Angular</strong>, and <strong>Protocol Buffers</strong> for a reward.</p>
<p dir="auto">A few important details about what still works:</p>
<ul>
<li>Reports about <strong>supply chain compromises</strong> are still accepted.</li>
<li>Reports filed before <strong>October 1</strong> remain in scope for review under the previous process.</li>
</ul>
<p dir="auto">The change follows a surge in invalid automated reports, which appears to have pushed Google to narrow the program's intake while it reassesses how product-level findings in OSS code are handled.</p>
<p dir="auto">Source: <a href="https://thehackernews.com/2026/10/google-pauses-oss-product-bug-bounty.html" target="_blank" rel="noopener noreferrer nofollow ugc">The Hacker News</a><br />
Has your team adjusted its OSS disclosure workflow since this pause took effect?</p>
]]></description><link>https://xploitlk.com/topic/669/google-pauses-oss-product-bug-bounty-rewards-after-surge-in-invalid-automated-reports</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 08:53:58 GMT</lastBuildDate><atom:link href="https://xploitlk.com/topic/669.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 13 Oct 2026 06:30:22 GMT</pubDate><ttl>60</ttl></channel></rss>