<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bug-Bounty on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/bug-bounty/</link><description>Recent content in Bug-Bounty on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 23 Jun 2026 12:12:16 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/bug-bounty/index.xml" rel="self" type="application/rss+xml"/><item><title>Google Told the Researcher Nice Catch Then Refused to Pay and Never Fixed It</title><link>https://hackingpassion.com/configconfusion-google-no-bounty/</link><pubDate>Tue, 23 Jun 2026 12:12:16 +0200</pubDate><guid>https://hackingpassion.com/configconfusion-google-no-bounty/</guid><description>&lt;p>Google told a security researcher his bug was a nice catch, lined up his payout, then eleven days later called it harmless and refused to pay a cent. The flaw he reported lets anyone with basic Kubernetes access take over a complete Google Cloud organization in about five seconds, with three lines of text and no special permissions at all. Months on, it still is not fixed. He named it &lt;strong>ConfigConfusion&lt;/strong>.&lt;/p></description></item><item><title>Six Working Windows Zero Days and the Researcher Microsoft Called a Criminal</title><link>https://hackingpassion.com/nightmare-eclipse-microsoft-zero-day-war/</link><pubDate>Sun, 31 May 2026 15:08:03 +0200</pubDate><guid>https://hackingpassion.com/nightmare-eclipse-microsoft-zero-day-war/</guid><description>&lt;p>Six working Windows attacks are sitting in the open right now, three of them already seen in a real intrusion, and the researcher who published them did it after he says Microsoft refused him, deleted the account he reported bugs through, and paid him nothing. Microsoft removed his account, called his actions criminal, and pointed at its crime unit. Both stories are out there, and the security world cannot agree on who is more to blame.&lt;/p></description></item><item><title>GitHub RCE CVE-2026-3854: One Semicolon, Millions of Private Repositories</title><link>https://hackingpassion.com/github-rce-cve-2026-3854/</link><pubDate>Wed, 29 Apr 2026 11:54:47 +0200</pubDate><guid>https://hackingpassion.com/github-rce-cve-2026-3854/</guid><description>&lt;p>&lt;strong>GitHub RCE CVE.&lt;/strong> A semicolon broke GitHub. One character in a push option field, and a security researcher was running code on the backend servers that store private repositories from millions of users and organizations. The git service user that processes every push on those servers has filesystem access to every repository on the node, and that access does not check who the repository belongs to. Private code from banks, hospitals, governments, and individual developers all sits on the same shared infrastructure. The command that got the researcher there is something every developer already runs every day.&lt;/p></description></item></channel></rss>