{"id":60897,"date":"2026-06-18T15:00:00","date_gmt":"2026-06-18T15:00:00","guid":{"rendered":"https:\/\/www.theregister.com\/a\/5258076"},"modified":"2026-06-18T15:00:00","modified_gmt":"2026-06-18T15:00:00","slug":"google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/","title":{"rendered":"Google told researcher &#8216;Nice catch!&#8217; Then denied bug bounty for flaw it still hasn&#8217;t fixed"},"content":{"rendered":"<div><img decoding=\"async\" src=\"https:\/\/image.theregister.com\/5258119.jpg?imageId=5258119&amp;x=0&amp;y=0&amp;cropw=100&amp;croph=100&amp;panox=0&amp;panoy=0&amp;panow=100&amp;panoh=100&amp;width=1200&amp;height=683\" class=\"ff-og-image-inserted\"><\/div>\n<p><span class=\"font-weight-bold m-font-weight-bold tertiary color_mobile_tertiary\" data-lab-font_weight=\"font-weight-bold\" data-lab-text_color=\"tertiary\">EXCLUSIVE<\/span><span class=\"font-weight-bold m-font-weight-bold \" data-lab-font_weight=\"font-weight-bold\">&nbsp;<\/span><span class=\"primary color_mobile_primary \" data-lab-text_color=\"primary\">Google has a security hole in a Kubernetes operator that could allow attackers to bypass Google Cloud Platform (GCP)<\/span> identity and access <span class=\"primary color_mobile_primary \" data-lab-text_color=\"primary\">protections and gain full control over any organization&#8217;s cloud environment. Or it has a serious communication and transparency problem when it comes to its bug bounty programs. <\/span><\/p>\n<p><span class=\"primary color_mobile_primary \" data-lab-text_color=\"primary\">Maybe both.<\/span><\/p>\n<p>Researcher and frequent cloud bug hunter Justin O&#8217;Leary told us that he found and reported to Google a major flaw that allows any Kubernetes namespace user to bypass GCP&#8217;s&nbsp;Identity and Access Management (IAM) controls and therefore gain root access to managing an organization&#8217;s cloud resources.&nbsp; <\/p>\n<p>Google initially rated the bug high priority and high severity, with a rep telling O&#8217;Leary &#8220;Nice Catch!&#8221; Then, the cloud giant changed course and told&nbsp;O&#8217;Leary and <span class=\"italic m-italic \" data-lab-italic=\"italic\">The Register<\/span> that there&#8217;s no vulnerability, so no fix and no reward payout. <\/p>\n<p>The bug report, however, is still marked high-priority and accepted.<\/p>\n<p>O&#8217;Leary spoke exclusively with <span class=\"italic m-italic \" data-lab-italic=\"italic\">The Register<\/span> about the vulnerability, which he named ConfigConfusion, and what has happened since he reported it to Google on March 8. He is also releasing a <a href=\"https:\/\/olearysec.com\/research\/config-connector-authorization-bypass\" rel=\"nofollow\">blog post<\/a> with more details.<\/p>\n<p>It stems from an issue in Config Connector, an open source Kubernetes add-on that lets users manage Google Cloud resources through Kubernetes. <\/p>\n<p>According to O&#8217;Leary, Config Connector doesn&#8217;t perform an authorization check, and this allows any Config Connector service account with org-level permissions to bypass Identity and Access Management (IAM)<span data-lab-text_color=\"primary\"> <\/span> authorization and gain the highest level of control (roles\/owner) to an entire GCP Organization \u2013 the root node of all of a company&#8217;s resources within Google Cloud.<\/p>\n<p>On March 27, a Google security engineer accepted O&#8217;Leary&#8217;s report and told him: &#8220;Nice catch!&#8221;<\/p>\n<p>The employee said that they filed a bug based on O&#8217;Leary&#8217;s report with the relevant product team and assured him the Chocolate Factory&#8217;s security squad would work with relevant Google Cloud people to fix the flaw.<\/p>\n<p>&#8220;We&#8217;ll work with the product team to ensure this issue is address. We&#8217;ll let you know when the issue was fixed,&#8221; the engineer said. &#8220;In the meantime, review the payment option selected in your bughunters.google.com profile.&#8221;<\/p>\n<p>Google assigned the bug <a href=\"https:\/\/developers.google.com\/issue-tracker\/concepts\/issues\">P1 priority<\/a> and S1 severity, signifying a flaw worthy of urgent repair because it affects a large percentage of users and can disrupt core organizational functions.<\/p>\n<p>&#8220;I figured that was the end of that,&#8221; O&#8217;Leary said in a phone interview with <em>The Register<\/em>.<\/p>\n<p>Eleven days later, on April 7, he received a new message from a Google Security Bot reversing the earlier decision. <em>The Reg<\/em> viewed the email, and O&#8217;Leary included a screenshot in his Thursday writeup.<\/p>\n<p>The message said that the Cloud Vulnerability Reward Program panel decided that the &#8220;security impact of this issue does not meet the criteria to qualify for a reward.&#8221;<\/p>\n<p>After reviewing the bug report, Google determined the software &#8220;is working as intended,&#8221; the message continued. It also noted that the program&#8217;s decision not to pay a bounty &#8220;does not mean that the product team won&#8217;t fix the issue.&#8221;<\/p>\n<p>Nearly three months later, the case remains P1\/S1 with the status &#8220;in progress (accepted).&#8221; Google hasn&#8217;t assigned a CVE or issued a fix. O&#8217;Leary didn&#8217;t receive any reward for his research.<\/p>\n<p>This isn&#8217;t the first time this has happened to O&#8217;Leary \u2013 or other <a href=\"https:\/\/www.theregister.com\/security\/2026\/04\/19\/ai-vendors-response-to-security-flaws-it-wasnt-me\/5228722\">security researchers<\/a> <a href=\"https:\/\/www.theregister.com\/security\/2026\/04\/16\/mcp-design-flaw-puts-200k-servers-at-risk-researcher\/5222022\">submitting bug bounty reports<\/a>.<\/p>\n<p>O&#8217;Leary had a <a href=\"https:\/\/olearysec.com\/research\/azure-backup-aks-silent-patch\/\">similar experience with Microsoft<\/a> earlier this year. In a story that has become <a href=\"https:\/\/www.theregister.com\/security\/2026\/01\/20\/anthropic-quietly-fixed-flaws-in-its-git-mcp-server\/4676059\">all too familiar <\/a>among <a href=\"https:\/\/www.theregister.com\/security\/2025\/08\/20\/aws-patches-q-developer-after-prompt-injection-rce-demo\/827867\">bug hunters<\/a>, O&#8217;Leary disclosed a privilege escalation vulnerability in Azure Backup for AKS. Microsoft rejected his report \u2013 and then <a href=\"https:\/\/www.theregister.com\/security\/2020\/12\/07\/when-is-a-remote-code-execution-bug-in-teams-not-an-rce-when-microsoft-says-it-isnt-flaw-finder-discovers\/518274\">silently patched<\/a> the flaw without assigning a CVE or publishing a security advisory.<\/p>\n<p>&#8220;This is a pattern,&#8221; O&#8217;Leary told us. &#8220;This is just how these trillion-dollar companies deal with people like me. In my day job, we use GKE, and it&#8217;s incredibly frustrating on my end, when I find a critical vulnerability in the system that&#8217;s being widely used, and I can&#8217;t even get the vendor to patch their own stuff.&#8221;<\/p>\n<h3>Google&#8217;s response<\/h3>\n<p>When <span class=\"italic m-italic \" data-lab-italic=\"italic\">The Reg<\/span> asked Google about O&#8217;Leary&#8217;s situation, the company told us that it didn&#8217;t issue a bug bounty reward because there&#8217;s no vulnerability.<\/p>\n<p>\u201cThe issue reported does not qualify for a reward because the GCP IAM authorization bypass is only exploitable if an attacker has access to a Config Connector Service Account that\u2019s been granted the Organization Admin role by the organization (i.e., it is privileged),&#8221; a Google spokesperson said in an email to <span class=\"italic m-italic \" data-lab-italic=\"italic\">The Register<\/span>. <\/p>\n<p>&#8220;Additionally, an attacker would first need to gain entry to an organization&#8217;s environment (e.g., an exposed container) in order to leverage the privileged Config Connector instance and execute commands with administrative authority, such as the IAM bypass,&#8221; the spokesperson continued. &#8220;Granting this level of access to the Config Connector Service Account goes against Google Cloud\u2019s publicly shared best practices and the principle of least privilege.&#8221;<\/p>\n<p>Google did not answer <span class=\"italic m-italic \" data-lab-italic=\"italic\">The Register<\/span>&#8216;s questions about why the bug report case remains marked in progress \u2013 and not closed \u2013 on its end of things.<\/p>\n<p>O&#8217;Leary told us this is the same explanation he received. And he doesn&#8217;t buy it.<\/p>\n<p>Yes, the Config Connector service account does need org-level permissions to manage resources across multiple GKE clusters. But Google&#8217;s own <a href=\"https:\/\/docs.cloud.google.com\/config-connector\/docs\/how-to\/configure-iam-permissions\" rel=\"nofollow\">documentation instructs users how to do this<\/a>, he noted. We confirmed this as well.<\/p>\n<p>Moreover, &#8220;having those permissions doesn&#8217;t mean any namespace user should be able to abuse them,&#8221; O&#8217;Leary posited. &#8220;A developer with kubectl access to one namespace&nbsp;\u2013 and zero GCP IAM permissions&nbsp;\u2013 should not be able to become Organization Owner. They also shouldn&#8217;t be able to impersonate any service account in the project with no audit trail.&#8221;<\/p>\n<p>According to O&#8217;Leary: &#8220;The vulnerability is the missing authorization check. Config Connector executes privileged operations on behalf of users without verifying those users are authorized.&#8221;<\/p>\n<h3>Three lines, five seconds, full admin control<\/h3>\n<p>In a video demonstrating ConfigConfusion, O&#8217;Leary shows how an attacker can write three lines of YAML to achieve full administrative control of a GCP Organization in about five seconds.<\/p>\n<p>&#8220;Config Connector has these missing validation checks,&#8221; he said. &#8220;Config Connector is basically a Google-managed Kubernetes operator, and I found that having these missing validation checks creates these confused deputies, which means there&#8217;s no validation of who&#8217;s asking for what.&#8221;<\/p>\n<p><a href=\"https:\/\/en.wikipedia.org\/wiki\/Confused_deputy_problem\">Confused deputies<\/a> pose a major security challenge because they allow an entity that doesn&#8217;t have permission to perform an action to force a more-privileged entity to perform the action.<\/p>\n<p>To exploit this issue, a user with kubectl access to one namespace \u2013 and no GCP permissions \u2013 submits a malicious IAMPolicyMember, which escalates the attacker&#8217;s privileges.<\/p>\n<p>Config Connector passes the user-controlled organization ID directly to the GCP IAM API without performing an authorization check, making the user a GCP Organization owner. This gives the attacker full admin control over everything in the environment \u2013 projects, secrets, billing, and Gmail accounts.<\/p>\n<div data-element-guid=\"afe083ca-6701-48e9-9bd8-f8827dd7fb42\" class=\"lab4 column articleList layout_vertical imageLayout_left small-12 large-12 small-abs-12 large-abs-12 abs_grid_12 grid-vas-start mobile-grid-vas-start\">\n<div class=\"content border_width_0 border_width_mobile_0 border-radius-48 border-radius-mobile_48\">\n<h2 class=\"article-list-title t19 font-RobotoCondensed\">MORE CONTEXT<\/h2>\n<\/p><\/div>\n<\/div>\n<p>&#8220;And there&#8217;s no record of it,&#8221; O&#8217;Leary said.<\/p>\n<p>This is because &#8220;the attacker&#8217;s Kubernetes identity never touches GCP IAM,&#8221; he wrote in the disclosure. &#8220;Config Connector executes the request using its own elevated credentials.&#8221;<\/p>\n<h3>&#8216;Jenga&#8217; vulnerabilities<\/h3>\n<p>According to O&#8217;Leary, Google has fixed this confused-deputy issue twice before in different services that access GCP. Tenable Research documented those issues and reported them to Google.<\/p>\n<p>One, called <a href=\"https:\/\/www.tenable.com\/blog\/imagerunner-a-privilege-escalation-vulnerability-impacting-gcp-cloud-run\">ImageRunner<\/a>, abused permissions in Google Cloud Run to pull private Google Artifact Registry and Google Container Registry images in the same account. The second, <a href=\"https:\/\/www.tenable.com\/blog\/confusedcomposer-a-privilege-escalation-vulnerability-impacting-gcp-composer\">ConfusedComposer<\/a>, allowed an identity with edit permissions inside a Cloud Composer environment to escalate privileges to the default Cloud Build service account.<\/p>\n<p>&#8220;This privilege-escalation vulnerability in GCP builds upon a broader attack class of vulnerabilities in cloud services that we call &#8216;<a href=\"https:\/\/www.blackhat.com\/us-24\/briefings\/schedule\/#the-gcp-jenga-tower-hacking-millions-of-googles-servers-with-a-single-package-and-more-40083\">Jenga,<\/a>&#8216;&#8221; Tenable security researcher Liv Matan said at the time.<\/p>\n<p>ConfusedComposer &#8220;exploits the somewhat-hidden cloud provider misconfigurations related to cloud services permissions to escalate privileges beyond intended access levels,&#8221; Matan explained. &#8220;This variant highlights how attackers can abuse interconnected services the cloud provider automatically deploys behind the scenes, as part of a service-orchestration process.&#8221;<\/p>\n<p>Google ultimately added authorization checks to both Cloud Run and Cloud Composer. O&#8217;Leary says he doesn&#8217;t understand why Google can&#8217;t also add that check to Config Connector.<\/p>\n<p>Or perhaps he does.<\/p>\n<p>&#8220;It&#8217;s just me versus Google,&#8221; he said. &#8220;They can&#8217;t do that same level of gaslighting to Tenable because they have PR teams and legal teams to fight them. I&#8217;m just a guy saying I don&#8217;t understand how this is true&#8221; \u2013 that is, how something can be both a high-severity, high-priority bug and also working as intended.<\/p>\n<p>&#8220;And they just say: &#8216;Well, it is true.'&#8221; \u00ae<\/p>\n<p> <img decoding=\"async\" src=\"https:\/\/image.theregister.com\/?imageId=5258119&#038;width=800\">READ MORE <a href=\"https:\/\/www.theregister.com\/security\/2026\/06\/18\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/5258076\">HERE<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> EXCLUSIVE &#8216;Working as intended&#8217; for the win \u2026 again READ MORE HERE&#8230;<\/p>\n","protected":false},"author":2,"featured_media":60898,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"colormag_page_layout":"default_layout","footnotes":""},"categories":[63],"tags":[307],"class_list":["post-60897","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-the-register","tag-security"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.1 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Google told researcher &#039;Nice catch!&#039; Then denied bug bounty for flaw it still hasn&#039;t fixed 2026 | ThreatsHub Cybersecurity News<\/title>\n<meta name=\"description\" content=\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security &amp; Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Google told researcher &#039;Nice catch!&#039; Then denied bug bounty for flaw it still hasn&#039;t fixed 2026 | ThreatsHub Cybersecurity News\" \/>\n<meta property=\"og:description\" content=\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security &amp; Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/\" \/>\n<meta property=\"og:site_name\" content=\"ThreatsHub Cybersecurity News\" \/>\n<meta property=\"article:published_time\" content=\"2026-06-18T15:00:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/image.theregister.com\/5258119.jpg?imageId=5258119&amp;x=0&amp;y=0&amp;cropw=100&amp;croph=100&amp;panox=0&amp;panoy=0&amp;panow=100&amp;panoh=100&amp;width=1200&amp;height=683\" \/>\n<meta name=\"author\" content=\"TH Author\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@threatshub\" \/>\n<meta name=\"twitter:site\" content=\"@threatshub\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"TH Author\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\\\/\"},\"author\":{\"name\":\"TH Author\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/person\\\/12e0a8671ff89a863584f193e7062476\"},\"headline\":\"Google told researcher &#8216;Nice catch!&#8217; Then denied bug bounty for flaw it still hasn&#8217;t fixed\",\"datePublished\":\"2026-06-18T15:00:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\\\/\"},\"wordCount\":1499,\"publisher\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed.jpg\",\"keywords\":[\"Security\"],\"articleSection\":[\"The Register\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\\\/\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\\\/\",\"name\":\"Google told researcher 'Nice catch!' Then denied bug bounty for flaw it still hasn't fixed 2026 | ThreatsHub Cybersecurity News\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed.jpg\",\"datePublished\":\"2026-06-18T15:00:00+00:00\",\"description\":\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed.jpg\",\"contentUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed.jpg\",\"width\":100,\"height\":66},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Security\",\"item\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/tag\\\/security\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Google told researcher &#8216;Nice catch!&#8217; Then denied bug bounty for flaw it still hasn&#8217;t fixed\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\",\"name\":\"ThreatsHub Cybersecurity News\",\"description\":\"%%focuskw%% Threat Intel \u2013 Threat Intel Services \u2013 CyberIntelligence \u2013 Cyber Threat Intelligence - Threat Intelligence Feeds - Threat Intelligence Reports - CyberSecurity Report \u2013 Cyber Security PDF \u2013 Cybersecurity Trends - Cloud Sandbox \u2013- Threat IntelligencePortal \u2013 Incident Response \u2013 Threat Hunting \u2013 IOC - Yara - Security Operations Center \u2013 SecurityOperation Center \u2013 Security SOC \u2013 SOC Services - Advanced Threat - Threat Detection - TargetedAttack \u2013 APT \u2013 Anti-APT \u2013 Advanced Protection \u2013 Cyber Security Services \u2013 Cybersecurity Services -Threat Intelligence Platform\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\"},\"alternateName\":\"Threatshub.org\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\",\"name\":\"ThreatsHub.org\",\"alternateName\":\"Threatshub.org\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/Threatshub_Favicon1.jpg\",\"contentUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/Threatshub_Favicon1.jpg\",\"width\":432,\"height\":435,\"caption\":\"ThreatsHub.org\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/x.com\\\/threatshub\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/person\\\/12e0a8671ff89a863584f193e7062476\",\"name\":\"TH Author\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"caption\":\"TH Author\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Google told researcher 'Nice catch!' Then denied bug bounty for flaw it still hasn't fixed 2026 | ThreatsHub Cybersecurity News","description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/","og_locale":"en_US","og_type":"article","og_title":"Google told researcher 'Nice catch!' Then denied bug bounty for flaw it still hasn't fixed 2026 | ThreatsHub Cybersecurity News","og_description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","og_url":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/","og_site_name":"ThreatsHub Cybersecurity News","article_published_time":"2026-06-18T15:00:00+00:00","og_image":[{"url":"https:\/\/image.theregister.com\/5258119.jpg?imageId=5258119&amp;x=0&amp;y=0&amp;cropw=100&amp;croph=100&amp;panox=0&amp;panoy=0&amp;panow=100&amp;panoh=100&amp;width=1200&amp;height=683","type":"","width":"","height":""}],"author":"TH Author","twitter_card":"summary_large_image","twitter_creator":"@threatshub","twitter_site":"@threatshub","twitter_misc":{"Written by":"TH Author","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/#article","isPartOf":{"@id":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/"},"author":{"name":"TH Author","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/person\/12e0a8671ff89a863584f193e7062476"},"headline":"Google told researcher &#8216;Nice catch!&#8217; Then denied bug bounty for flaw it still hasn&#8217;t fixed","datePublished":"2026-06-18T15:00:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/"},"wordCount":1499,"publisher":{"@id":"https:\/\/www.threatshub.org\/blog\/#organization"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/#primaryimage"},"thumbnailUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2026\/06\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed.jpg","keywords":["Security"],"articleSection":["The Register"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/","url":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/","name":"Google told researcher 'Nice catch!' Then denied bug bounty for flaw it still hasn't fixed 2026 | ThreatsHub Cybersecurity News","isPartOf":{"@id":"https:\/\/www.threatshub.org\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/#primaryimage"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/#primaryimage"},"thumbnailUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2026\/06\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed.jpg","datePublished":"2026-06-18T15:00:00+00:00","description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","breadcrumb":{"@id":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/#primaryimage","url":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2026\/06\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed.jpg","contentUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2026\/06\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed.jpg","width":100,"height":66},{"@type":"BreadcrumbList","@id":"https:\/\/www.threatshub.org\/blog\/google-told-researcher-nice-catch-then-denied-bug-bounty-for-flaw-it-still-hasnt-fixed\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.threatshub.org\/blog\/"},{"@type":"ListItem","position":2,"name":"Security","item":"https:\/\/www.threatshub.org\/blog\/tag\/security\/"},{"@type":"ListItem","position":3,"name":"Google told researcher &#8216;Nice catch!&#8217; Then denied bug bounty for flaw it still hasn&#8217;t fixed"}]},{"@type":"WebSite","@id":"https:\/\/www.threatshub.org\/blog\/#website","url":"https:\/\/www.threatshub.org\/blog\/","name":"ThreatsHub Cybersecurity News","description":"%%focuskw%% Threat Intel \u2013 Threat Intel Services \u2013 CyberIntelligence \u2013 Cyber Threat Intelligence - Threat Intelligence Feeds - Threat Intelligence Reports - CyberSecurity Report \u2013 Cyber Security PDF \u2013 Cybersecurity Trends - Cloud Sandbox \u2013- Threat IntelligencePortal \u2013 Incident Response \u2013 Threat Hunting \u2013 IOC - Yara - Security Operations Center \u2013 SecurityOperation Center \u2013 Security SOC \u2013 SOC Services - Advanced Threat - Threat Detection - TargetedAttack \u2013 APT \u2013 Anti-APT \u2013 Advanced Protection \u2013 Cyber Security Services \u2013 Cybersecurity Services -Threat Intelligence Platform","publisher":{"@id":"https:\/\/www.threatshub.org\/blog\/#organization"},"alternateName":"Threatshub.org","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.threatshub.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.threatshub.org\/blog\/#organization","name":"ThreatsHub.org","alternateName":"Threatshub.org","url":"https:\/\/www.threatshub.org\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2025\/05\/Threatshub_Favicon1.jpg","contentUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2025\/05\/Threatshub_Favicon1.jpg","width":432,"height":435,"caption":"ThreatsHub.org"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/threatshub"]},{"@type":"Person","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/person\/12e0a8671ff89a863584f193e7062476","name":"TH Author","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","caption":"TH Author"}}]}},"_links":{"self":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts\/60897","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/comments?post=60897"}],"version-history":[{"count":0,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts\/60897\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/media\/60898"}],"wp:attachment":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/media?parent=60897"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/categories?post=60897"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/tags?post=60897"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}