UPLINK OK // SYNC 13M AGO

// writeups · what the crowd found, ranked by the crowd

READ THE LOGS

Bug bounty writeups from Medium, Infosec Writeups, r/bugbounty, Standoff 365 disclosed reports and the pentester.land archive, linked to the programs they're about. Vote up what's worth your time. No account needed.

writeups about Google ✕ all

JSON ↗
  1. 1.
    Google Paid $250,000 for One Chrome Bug Chain. It Took Six Days. (medium.com)
    0 points · by ZXVE · · medium · google cybersecurityartificial-intelligencebug-bountyethical-hacking

    Imagine opening a web page in Chrome.

  2. 2.
    AI Found a Bug That Google’s Best Testing Missed. Here Is What That Means for Bug Hunters (medium.com)
    0 points · by Duckey Longbottom · · medium · google cybersecuritytechnologybug-bountyai

    What if the hardest bug to find was not hidden from you, but hidden from every tool we trusted for years? In late 2024, Google’s Big Sleep…

  3. 3.
    I Found a 9.8 Critical Integer Overflow in Google’s TensorFlow. Google Refused to Pay Me. (medium.com)
    0 points · by Aser Ahmed · · medium · google bug-bountyinfoseccybersecuritytensorflow
  4. 4.
    Google Paid Bug Hunters $17.1M. AI Bias Bounties Topped Out at $24K (briefs.aiadvances.org)
    0 points · by Brian Rain · · medium · google responsible-aiartificial-intelligencebug-bountyai-ethics

    Security built bug bounties and safe harbor for outsiders. AI ethics left self-taught practitioners nowhere to practice.

  5. 5.
    Google Cloud announces a $250,000 top bug bounty reward. What makes this interesting (reddit.com)
    0 points · by UniversityMammoth653 · · reddit · google

    Google Cloud announced a new $250,000 top reward under its Cloud Vulnerability Reward Program on October 29, 2026. But the interesting part isn't just the payout. It's the type of vulnerability Google wants researchers to find. The new reward tier targets vulnerabilities that…

  6. 6.
    [$10,000] Google Jules — The Silent Code Heist - Stealing Github Codes Remotely (medium.com)
    0 points · by Avinash Kumar · · medium · github · google bug-bounty-hunterbug-bounty-tipsbug-bounty-writeupbug-bounty

    Hi everyone!

  7. 7.
    Google classified my report as P1/S1. 180 days later, the issues are still reproducible. Reward: $0. Is this normal? (reddit.com)
    0 points · by Yone_welsch · · reddit · google

    ​ I'm an independent user who has been documenting unusual Gemini behaviors on Android for several months. I submitted a vulnerability report through Google's Vulnerability Reward Program (VRP). Google officially upgraded the ticket: - Type: Customer Issue → Bug - Priority:…

  8. 8.
    I Found an Account Takeover Vulnerability Through Google Dorking | by Samadhan Shimple (radiohackers.com)
    0 points · by Samadhan shimple · · medium · google google-dorkpenetration-testingbug-bountycybersecurity

    Sometimes, finding a security vulnerability is not about using advanced tools or running complicated scripts. Sometimes, it starts with a…

  9. 9.
    I Found an Account Takeover Vulnerability Through Google Dorking | by Samadhan Shimple (samadhanshimple.medium.com)
    0 points · by Samadhan shimple · · medium · google google-dorkpenetration-testingbug-bountycybersecurity

    Sometimes, finding a security vulnerability is not about using advanced tools or running complicated scripts. Sometimes, it starts with a…

  10. 10.
    When Google Becomes Attacker-Controlled: Finding an SSO Validation Flaw (1yz02.medium.com)
    0 points · by Yahya Hammam · · medium · google bug-bountycybersecurity

    Hi Hackers ,

  11. 11.
    Intel Closed Its Bug Bounty. Google Paused Its. curl Quit. I’m Still Here. (medium.com)
    0 points · by Riya Limba · · medium · google · intel cybersecuritybug-bounty-tipsbug-bountyethical-hacking

    The programs are dying because AI made filing a fake report cheaper than ever. That doesn’t mean the work is gone.

  12. 12.
    Google paid me $90,000 for this RCE (reddit.com)
    0 points · by TradeGold6317 · · reddit · google

    submitted by /u/TradeGold6317 [link] [comments]

  13. 13.
    How I Got Bugs From Google Dorks (ch44nd.medium.com)
    0 points · by Chandan das · · pentesterland · google Information disclosure
  14. 14.
    How I can easily get four P1 at NASA using Simple Google Dorking. (k4tedu.medium.com)
    0 points · by Francesco Topol / k4tedu · · pentesterland · google Information disclosure
  15. 15.
    Google AI Studio: LLM-Powered Data Exfiltration Hits Again! Quickly Fixed. (embracethered.com)
    0 points · by Johann Rehberger (wunderwuzzi23) · · pentesterland · google AILLMPrompt injection
  16. 16.
    How I Got Critical P2 Bug on Google VRP (medium.com)
    0 points · by Kazi Hashibur Rahman · · pentesterland · google Missing authenticationInformation disclosure
  17. 17.
    Escalating Privileges in Google Cloud via Open Groups (netspi.com)
    0 points · by Thomas Elling · · pentesterland · google CloudPrivilege escalation
  18. 18.
    Interesting Business Logic Error leads to Pre-Account Takeover via Verification bypass on GoogleVRP (medium.com)
    0 points · by Jerry1319 (@Mdhsan19) · · pentesterland · google Account takeoverLogic flaw
  19. 19.
    Leaking All Users Google Drive Files (secreltyhiddenwriteups.blogspot.com)
    0 points · by Cam (@SecretlyHidden1) · · pentesterland · google Broken Access Control
  20. 20.
    Unveiling TE.0 HTTP Request Smuggling: Discovering a Critical Vulnerability in Thousands of Google Cloud Websites (bugcrowd.com)
    0 points · by Paolo Arnolfo (@sw33tLie), Guillermo Gregorio (@bsysop), Francesco Mariani (@_medusa_1_) · · pentesterland · $8,500 · google HTTP request smugglingCloud
  21. 21.
    Shelltorch Explained: Multiple Vulnerabilities in Pytorch Model Server (Torchserve) (CVSS 9.9, CVSS 9.8) Walkthrough (oligo.security)
    0 points · by Gal Elbaz, Uri Katz, Guy Kaplan, Avi Lumelsky · · pentesterland · google AILLMRCESSRF
  22. 22.
    The Monsters in Your Build Cache – GitHub Actions Cache Poisoning (adnanthekhan.com)
    0 points · by Adnan Khan (@adnanthekhan) · · pentesterland · $1,000 · google · github CI/CDSupply chain attack
  23. 23.
    CVE-2024-2887: A Pwn2Own Winning Bug In Google Chrome (zerodayinitiative.com)
    0 points · by Manfred Paul (@_manfp) · · pentesterland · google · google-chrome V8 JavaScript engineWebAssemblyJS sandbox breakoutBrowser hacking
  24. 24.
    LeakyCLI: AWS and Google Cloud Command-Line Tools Can Expose Sensitive Credentials in Build Logs (orca.security)
    0 points · by Roi Nisimi (@roinisimi) · · pentesterland · google Information disclosure
  25. 25.
    An Obscure Actions Workflow Vulnerability in Google’s Flank (adnanthekhan.com)
    0 points · by Adnan Khan (@adnanthekhan) · · pentesterland · $7,500 · google CI/CDSupply chain attack
  26. 26.
    Google AI Studio Data Exfiltration via Prompt Injection - Possible Regression and Fix (embracethered.com)
    0 points · by Johann Rehberger (wunderwuzzi23) · · pentesterland · google LLMAIPrompt injectionData leak
  27. 27.
    New Google Gemini Vulnerability Enabling Profound Misuse (hiddenlayer.com)
    0 points · by Kenneth Yeung · · pentesterland · google AILLMLLM JailbreakIndirect Prompt Injection
  28. 28.
    We Hacked Google A.I. for $50,000 (landh.tech)
    0 points · by Roni Carta (@0xLupin) · · pentesterland · $50,000 · google LLMAIGraphQLDoS
  29. 29.
    How I hacked into Google’s internal corporate assets (observationsinsecurity.com)
    0 points · by Michael Hyndman · · pentesterland · google Dependency confusionRCESupply chain attack
  30. 30.
    CSP bypass on PortSwigger.net using Google script resources (joaxcar.com)
    0 points · by Johan Carlsson (@joaxcar) · · pentesterland · $1,500 · google CSP bypass