Skip to content

Google bug bounty programs

google.com Updated

Google runs 16 public programs on its own site and Sorona; 16 pay cash, the most up to $1,500,000 (Android and Google Devices Security Rewards). 14 companies it owns, including google.github.io and Chromium, run 18 more programs.

Top reward
$1,500,000
Self-hosted
Programs
34
33 pay cash
Targets in scope
277
8 types, deduplicated
Last change
None yet
Tracked since Nov 2026

Where to report

16 programs Google runs itself, side by side. Report where the affected target is in scope; when two programs cover it, pick the one that pays more.

Start here

Google and Alphabet VRP

Self-hosted · The company-wide program. Pays up to $101,010.

Amounts are the top reward per severity in the currency each program pays. Green marks the highest per severity. First response is the platform's measured average when it publishes one, else what the policy promises.

Companies Google owns

14 companies with 18 programs of their own. Each has its own scope and rules: report to the one that owns the asset.

What is in scope

277 targets across all 34 programs, each listed once with the programs that cover it. 166 excluded.

  • *.blogger.com

    Wildcards

    Covered by Google and Alphabet VRP

  • *.deepmind.com

    Wildcards

    Covered by Google and Alphabet VRP

  • *.google.com

    Wildcards

    Covered by Google and Alphabet VRP

  • *.gousto.co.uk

    Wildcards No bounty

    Covered by Google and Alphabet VRP

  • *.gousto.ie

    Wildcards No bounty

    Covered by Google and Alphabet VRP

  • *.projectbaseline.com

    Wildcards Low

    Covered by HackerOne

  • *.signalpath.com

    Wildcards Critical

    Covered by HackerOne

  • *.verily.com

    Wildcards Critical

    Covered by HackerOne

  • *.verilyme.com

    Wildcards Critical

    Covered by HackerOne

  • *.waymo.com

    Wildcards

    Covered by Google and Alphabet VRP

  • *.wing.com

    Wildcards

    Covered by Google and Alphabet VRP

  • *.youtube.com

    Wildcards

    Covered by Google and Alphabet VRP

  • android.com

    Domains

    Covered by Android and Google Devices Security Rewards

  • bc.googleusercontent.com

    Domains

    Covered by Google Cloud VRP

  • blogger.com

    Domains

    Covered by Google and Alphabet VRP

  • chromium.org

    Domains

    Covered by ChromeOS VRP, Chrome Vulnerability Rewards

  • deepmind.com

    Domains

    Covered by Google and Alphabet VRP

  • github.com

    Domains

    Covered by Google Open Source Software VRP, Google Patch Rewards

  • google search (on google.com)

    Domains

    Covered by Google AI VRP

  • googleusercontent.com

    Domains

    Covered by Google Cloud VRP

  • gousto.co.uk

    Domains No bounty

    Covered by Google and Alphabet VRP

  • gousto.ie

    Domains No bounty

    Covered by Google and Alphabet VRP

  • pub.dev

    Domains

    Covered by security.txt

  • waymo.com

    Domains

    Covered by Google and Alphabet VRP

No target matches. Try part of a host name, such as the company name.

Out of scope 166

Don't test these. A program can exclude a host another program covers; the program you report to decides.

  • *.appspot.com

    Google Cloud VRP Google and Alphabet VRP

  • *.bc.googleusercontent.com

    Google and Alphabet VRP Google Cloud VRP

  • *.blogspot.com

    Google and Alphabet VRP

  • *.googleusercontent.com

    Google and Alphabet VRP

  • Agent output that is merely wrong or undesirable, with no concrete security boundary crossed

    Agent Development Kit

  • Already-patched 1-day bugs, since the program buys 0-days demonstrated live

    kvmCTF (Linux KVM hypervisor)

  • AngularJS 1.x, which is end-of-life and does not appear in the tier file at any band

    Angular

  • Any Google repository absent from the tier file, which sits at OT2 or OT3 and pays nothing for a product vulnerability

    Dart SDK

  • Any other repository in the jax-ml, openxla or Google orgs that the tier file does not list, which pays nothing for a product vulnerability after the April 2026 rules update

    JAX and OpenXLA

  • Anything below the High or Critical bar the scope sentence sets, along with low-quality submissions, which are capped at the $500 base amount regardless of the class of bug described

    Chromium

  • Anything on the published Android threat-model non-bug list, closed as unactionable and ineligible for a reward

    Android Virtualization Framework and pKVM

  • Anything privately disclosed to a third party before Google: the VRP states that such reports will typically not qualify for a reward

    Tink

  • Anything short of a demonstrated, working exploit. A crash, a theoretical write primitive or a patch on its own does not qualify

    kernelCTF (Linux kernel LTS)

  • Anything shown only against a locally built kernel rather than against Google's pinned instance

    kvmCTF (Linux KVM hypervisor)

  • Anything that depends on unprivileged user namespaces, disabled on the instance since 1 July 2025 precisely because that surface was producing too many winning exploits

    kernelCTF (Linux kernel LTS)

  • Anything you cannot reproduce on an in-support Google device, so a result that only holds on an emulator or an out-of-support handset does not qualify

    Android Virtualization Framework and pKVM

  • API misuse by a hypothetical caller. A badly written policy in someone else's integration is that integration's defect, and the finding has to weaken a real confinement on ChromeOS

    minijail

  • Application-level XSS in a site that happens to use TensorFlow.js but whose flaw is in the site's own code

    TensorFlow.js

  • Applications written in Flutter rather than defects in the framework that ships to them

    Flutter

  • Attacks that require a rooted device

    Google Mobile VRP

  • Automated scanner or fuzzer output submitted without triage, a reproducer, or root-cause analysis

    Go

  • Awards to researchers on a sanctions list, in a territory subject to sanctions, or located in Russia or Belarus, which Google states it cannot pay

    TensorFlow.js Dart SDK TensorFlow Serving

  • Awards to researchers on sanctions lists, in territories subject to sanctions, or located in Russia or Belarus, which Google states it will not issue

    Flutter Angular Agent Development Kit Bazel

  • Backend and server-side services, which route to the main Google VRP rather than to this program

    Android Virtualization Framework and pKVM

  • Browser engine bugs, which belong to the browser vendor's own program rather than to the library running inside it

    TensorFlow.js

  • Bugs in applications built with Angular rather than defects in the framework itself

    Angular

  • Bugs that actually live in a downstream wrapper such as ImageMagick, Pillow, GD or a language binding, rather than in libwebp itself

    libwebp

  • Bugs that are not actually present in a Go package (misattributed user-code issues)

    Go

  • Build breakage, incorrect output and performance regressions that carry no security consequence

    Bazel

  • CIDR blocks or IP ranges allocated to Google Cloud customers

    Google Cloud VRP

  • Code on trunk less than seven days old, which has not reached any shipping channel

    libwebp Chromium

  • Compiling or executing code the caller already controls, since that sits inside the trust boundary the framework assumes

    JAX and OpenXLA

  • CPU, DRAM and other hardware-based issues, the Spectre, MDS and Rowhammer families among them, which are not rewarded here

    kvmCTF (Linux KVM hypervisor)

  • Crashes a reboot recovers from, since the rules only treat a crash as a vulnerability where restart is not possible

    minijail

  • Cryptanalysis of the standard primitives themselves with no Tink-specific exploitation path, which attacks the algorithm rather than this code

    Tink

  • customer instances, databases, storage buckets, or applications

    Google Cloud VRP

  • Debug-mode-only behaviour that is documented as insecure and disabled in release builds

    Flutter

  • debugging features

    Chrome Vulnerability Rewards

  • Defects that only reproduce on a plugin release wordpress.org no longer carries, since the program covers the latest versions

    Site Kit by Google

  • Defects that only reproduce on a release the project no longer ships, since the program covers the latest versions

    Protocol Buffers gVisor Dart SDK TensorFlow Serving TensorFlow TensorFlow.js

  • Defects that only reproduce on a release the projects no longer ship, since the program covers the latest versions

    JAX and OpenXLA

  • Denial of service against the sandbox itself where there is no escape and no impact on the host or other tenants

    gVisor

  • Denial of service produced by legitimate load, as opposed to a single malformed request that takes the server down

    TensorFlow Serving

  • Denial-of-service or panics with no security-relevant impact beyond a crash, and issues that only affect Go releases already fixed in the two most recent major versions

    Go

  • Developer-machine-only issues in adk web absent a realistic attack path to reach them

    Agent Development Kit

  • Developer-machine-only issues in the CLI dev server where you cannot describe a realistic attack scenario

    Angular

  • Devices within 90 days of the end of their guaranteed security updates

    Android Runtime (ART) and libcore

  • Documentation-only findings against google.github.io/minijail/, which the ChromeOS VRP rules name by URL as ineligible

    minijail

  • Downstream misconfiguration of runsc by a platform operator rather than a defect in what runsc ships

    gVisor

  • Downstream misuse of protobuf APIs that are documented to require already-sanitised input

    Protocol Buffers

  • Duplicates and late entries: "Only the first submission for a vulnerability is eligible for a reward (per target)", and there is one paid slot per LTS kernel version

    kernelCTF (Linux kernel LTS)

  • Encoder-only bugs with no decode path from untrusted input, since nobody feeds an attacker's bytes to the encoder

    libwebp

  • Experimental features

    Chrome Vulnerability Rewards

  • Experimental features, debugging features and unsafe browser flags, per the Chrome VRP's standard exclusions

    libwebp

  • Experimental features, debugging features and unsafe flags, none of which represent a configuration users are exposed to

    Chromium

  • Findings already subsumed by an entry in the Go vulnerability database, or documented as expected behavior in Go's published vulnerability-classification decisions

    Go

  • Flutter itself (flutter/flutter), which Google rates OT0 and prices on its own entry rather than this one

    Dart SDK

  • Generic upstream Linux kernel bugs without an Android-specific proof of concept, even where the code path is shared

    Android Virtualization Framework and pKVM

  • Google backend services and server-side APIs, which belong to the separate Google and Alphabet VRP rather than to this program

    Android Runtime (ART) and libcore

  • Google infrastructure, backend APIs, or server-side services interacting with these devices

    Android and Google Devices Security Rewards

  • Google repositories the tier file does not name, which sit at OT2 or OT3 and pay nothing for a product vulnerability

    TensorFlow.js TensorFlow Serving

  • Google Workspace products

    Google Cloud VRP

  • Google's production environment, Borg

    Google Cloud VRP

  • GPU vendor driver and CUDA bugs that merely surface through XLA and belong to the hardware vendor

    JAX and OpenXLA

  • Hardcoded API keys

    Google Mobile VRP

  • Host kernel bugs that gVisor does not mediate, which belong to the kernel rather than to the sandbox

    gVisor

  • Individuals and entities in Russia or Belarus, who cannot be paid, along with anyone else the sanctions rules reach

    Android Runtime (ART) and libcore

  • Insecure application configuration chosen by a downstream integrator

    Angular

  • Insider-only risks, which the rules downgrade to credit rather than a reward

    Bazel

  • io_uring and nftables, both disabled on the target for the same reason

    kernelCTF (Linux kernel LTS)

  • Issues already covered by Android's published threat models and known-non-bug list

    Android Runtime (ART) and libcore

  • Issues that only manifest with the device in Developer mode

    minijail

  • Issues that require a malicious BUILD or MODULE.bazel file the developer already chose to run, absent a realistic non-maintainer attack path

    Bazel

  • Issues that require an administrator account acting against their own site, since an administrator already holds the capability being bypassed

    Site Kit by Google

  • Issues that require an already-privileged host operator, since that is inside the trust boundary

    gVisor

  • Kernel subsystems outside KVM, which belong to kernelCTF or to the kernel's own security process rather than to this program

    kvmCTF (Linux KVM hypervisor)

  • Kernel versions other than the LTS the instance is currently running, which rotates every two to four weeks on average

    kernelCTF (Linux kernel LTS)

  • Key-management failures in the integrating application, such as a caller writing an unencrypted keyset to disk

    Tink

  • Loading an intentionally malicious model, where the documentation already warns that models are code

    TensorFlow

  • LTS-channel-only findings and hardware past its auto-update expiry, both outside the supported configuration the program pays on

    minijail

  • Memory-corruption reports against tink-cc that arrive without OSS-Fuzz reproduction steps or a merged patch, since the program will not price them in that form

    Tink

  • Memory-corruption reports filed without exact OSS-Fuzz reproduction steps against an existing fuzz target, including how to build the image, or an already merged patch

    Dart SDK

  • Memory-corruption reports filed without exact OSS-Fuzz reproduction steps against an existing fuzz target, or an already merged patch

    TensorFlow Serving TensorFlow.js

  • Memory-corruption reports in XLA submitted without exact OSS-Fuzz reproduction steps against an existing fuzz target, or a merged upstream patch

    JAX and OpenXLA

  • Memory-corruption reports submitted without exact OSS-Fuzz reproduction steps against an existing fuzz target, or a merged upstream patch

    gVisor TensorFlow

  • Memory-corruption reports that arrive without exact OSS-Fuzz reproduction steps against an existing fuzz target, or a merged upstream patch

    Protocol Buffers

  • MiraclePtr-protected bugs

    Chrome Vulnerability Rewards

  • MiraclePtr-protected use-after-free in non-renderer processes, which the program now records as PROTECTED under BRP-ASAN rather than as a security bug

    Chromium

  • Model accuracy and adversarial-input research, which is ML robustness rather than a software vulnerability

    TensorFlow.js

  • Model-behaviour and ML-safety research, which the program routes to the Google AI VRP rather than the OSS VRP

    JAX and OpenXLA

  • Model-level adversarial-example and ML-robustness research, which is not a software vulnerability

    TensorFlow

  • Model-poisoning and adversarial-example research, which is ML robustness rather than a software vulnerability

    TensorFlow Serving

  • Non-Pixel OEM devices, which do not satisfy the hardware-reproduction requirement even when the underlying code is identical. The proof of concept has to run on the latest public build of supported Pixel, Nest or Fitbit hardware

    Android Runtime (ART) and libcore

  • Numerical accuracy differences with no security consequence, which are correctness bugs rather than vulnerabilities

    JAX and OpenXLA

  • Operator misconfiguration such as exposing the server to a network without authentication, which is documented behaviour rather than a defect

    TensorFlow Serving

  • other Google Cloud products

    Google AI VRP

  • Other open-source, non-proprietary, or third-party applications

    Google AI VRP

  • Other plugins and themes installed alongside Site Kit, including interactions that only misbehave because of what the other plugin does

    Site Kit by Google

  • Other repositories in the protocolbuffers org, which the tier file does not list and which pay nothing for a product vulnerability after the April 2026 rules update

    Protocol Buffers

  • Other repositories in the tensorflow org beyond the five the tier file lists, which pay nothing for a product vulnerability after the April 2026 rules update

    TensorFlow

  • other Tier 3 or Tier 4 applications

    Google AI VRP

  • Payment to individuals in Russia or Belarus, which the program's sanctions screening blocks

    Android Virtualization Framework and pKVM

  • Platform-specific bugs owned by Android or iOS rather than by Flutter's own code

    Flutter

  • Prompt injection framed purely as model behaviour rather than as a failure of a framework control, which the program routes to the Google AI VRP instead

    Agent Development Kit

  • Python-level API misuse by the caller rather than a defect in the framework

    TensorFlow

  • QEMU vulnerabilities, excluded explicitly despite QEMU being the userspace half of the same stack

    kvmCTF (Linux KVM hypervisor)

  • Recent acquisitions

    Google Cloud VRP

  • Reports filed by anyone other than the finder: Google wants the submission through bughunters.google.com under the researcher's own identity, and it does not pay Google or Google Partner employees

    TensorFlow Protocol Buffers Site Kit by Google gVisor JAX and OpenXLA

  • Reports filed by anyone other than the researcher: Google requires the submission under your own identity through bughunters.google.com, and treats routing around the designated channel as grounds to reject

    Agent Development Kit Flutter Bazel Angular

  • Reports filed outside bughunters.google.com with a Google Account, which the rules treat as typically not reward-eligible, and researchers in Russia or Belarus, whom sanctions screening bars from payment

    minijail

  • Reports filed to the Google OSS VRP instead of the Chrome VRP, where libwebp's absence from the tier file means a product vulnerability pays nothing

    libwebp

  • Reports that rely on highly improbable preconditions or unrealistic user interaction, and findings below the program's impact thresholds

    Android Virtualization Framework and pKVM

  • Repositories in Google's GitHub orgs that the tier file does not list, which pay nothing for a product vulnerability after the April 2026 rules update

    gVisor Site Kit by Google

  • Repositories the tier file does not name, and releases that are not current: the program covers the latest versions of the listed repositories, and any other repository in the same organisation counts only where the file names it. What the file omits sits at OT2 or OT3, where product vulnerabilities earn no monetary reward

    Flutter Angular Agent Development Kit Bazel

  • Resource-exhaustion crashes with negligible security impact under the project's own threat model

    Protocol Buffers

  • Rewards to researchers on a sanctions list, in a sanctioned territory, or located in Russia or Belarus, which Google states it cannot issue

    gVisor Protocol Buffers JAX and OpenXLA Site Kit by Google TensorFlow

  • Secondary lockscreen bypasses

    Google Mobile VRP

  • Server-side Google services, which route to the main Google VRP rather than to the Chrome program

    Chromium

  • Shell reports filed without a proof of concept to reserve a timestamp, which the program treats as noise against your account rating

    Android Virtualization Framework and pKVM

  • Site-owner misconfiguration of Google service permissions, which is a setup mistake rather than a plugin defect

    Site Kit by Google

  • social engineering attacks

    Google Open Source Software VRP

  • Social engineering, and issues only exploitable by someone who already has maintainer or commit access

    Dart SDK

  • Speculative reports that do not demonstrate the bug actually manifesting in Chrome

    Chromium

  • Speculative reports that do not demonstrate the bug manifesting in a shipping browser

    libwebp

  • Submissions from Google employees and from employees of Google partner companies developing code for covered devices

    Android Virtualization Framework and pKVM

  • Submissions that require a separately supplied KASLR base, which the 2026-04-30 rules removed as an option

    kernelCTF (Linux kernel LTS)

  • TensorFlow core kernel bugs, which belong to the TensorFlow entry rather than to the model server

    TensorFlow Serving

  • The Dart SDK and language runtime, which is a separate tier-file entry (dart-lang/sdk) with its own band

    Flutter

  • The full-chain rung is capped by budget as well as by difficulty: only four exploit bonuses will be paid in 2026, so a fifth complete chain has no band left to land on

    Chromium

  • The host-to-KVM direction, which is not the boundary this program prices

    kvmCTF (Linux KVM hypervisor)

  • The hosted sitekit.withgoogle.com service itself, which is a Google web property under the main Google VRP rather than the open-source program

    Site Kit by Google

  • The plugins in flutter/packages, which the tier file does not name, along with third-party packages published on pub.dev

    Flutter

  • Third-party Angular component libraries, which are not Google-maintained and are not covered by the tier file

    Angular

  • Third-party Bazel rulesets outside the bazelbuild organisation, which are not listed in Google's repository tier file

    Bazel

  • Third-party container runtimes that are not gVisor

    gVisor

  • Third-party or non-Go-project code; report those upstream first

    Go

  • Third-party protobuf reimplementations such as protobuf.js or gogo/protobuf, which are not in the tier file

    Protocol Buffers

  • Third-party pub.dev packages that Google does not own, which fall outside the tier file entirely

    Dart SDK

  • Third-party TensorFlow distributions and vendor forks, which are outside the tier file

    TensorFlow

  • Third-party Tink ports and reimplementations, which carry no tier-file line and therefore no price

    Tink

  • Third-party tools and MCP servers the developer chose to connect, which are their authors' code and not the framework's

    Agent Development Kit

  • Third-party websites

    Google Cloud VRP

  • Tier3 or Tier4 acquisitions

    Google AI VRP

  • Trustpilot

    Google and Alphabet VRP

  • Typosquatting and dependency confusion, unless it actually compromises the distributed build artifacts

    Protocol Buffers

  • Unreachable code paths, which the rules exclude outright: unreachable bugs do not qualify for reward

    minijail

  • unsafe flags

    Chrome Vulnerability Rewards

  • Upstream Linux kernel and generic Linux components, "unless the reporter provides a functional Proof of Concept demonstrating a direct, exploitable impact specifically on Android or Pixel-maintained modules"

    Android Runtime (ART) and libcore

  • upstream Linux kernel or generic Linux components

    Android and Google Devices Security Rewards

  • Variants of Strandhogg and Tapjacking

    Google Mobile VRP

  • Vertex AI

    Google AI VRP

  • Vertex AI and Gemini API service-side issues, which belong to the Cloud or AI VRP

    Agent Development Kit

  • Vulnerabilities impacting ChromeOS on unsupported hardware or AUE devices.

    ChromeOS VRP

  • Vulnerabilities in 3rd-party services or platforms used to maintain and build Google OSS (e.g. source code management systems, CI/CD systems, package managers)

    Google Open Source Software VRP

  • Vulnerabilities in Android

    ChromeOS VRP

  • Vulnerabilities in backend components and services

    ChromeOS VRP

  • Vulnerabilities in Go applications or non-importable code, including anything in package main or an installable command, which sit outside the Go vulnerability database's scope

    Go

  • Vulnerabilities in older releases available through our Long Term Stable (LTS) channel.

    ChromeOS VRP

  • Vulnerabilities in the Chrome Browser that are not ChromeOS-specific (in Ash/Aura Shell)

    ChromeOS VRP

  • Vulnerabilities in the third-party CI platforms Bazel uses, which the program rules place explicitly out of scope

    Bazel

  • Vulnerabilities that allow access to non-sensitive media in external storage

    Google Mobile VRP

  • Vulnerabilities that do not work on the latest available operating system version

    Google Mobile VRP

  • Vulnerabilities that only manifest when the device is in Developer mode.

    ChromeOS VRP

  • WebKit that impact Chrome on iOS

    Chrome Vulnerability Rewards

  • WordPress core vulnerabilities, which belong to WordPress rather than to the plugin

    Site Kit by Google

  • Zendesk

    Google and Alphabet VRP

Recent changes

Reward and scope changes across every Google program, newest first.

No changes recorded yet. New targets and reward moves show up here and in the RSS feed.

Recent CVEs

Published vulnerabilities in Google products, from the NVD.

Search NVD
  • Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.28, 21.2.20, and 22.1.1, Angular's @angular/common HttpTransferCache can cache an authenticated response when Server-Side Rendering (SSR) and hydration use a hierarchical HttpClient configured with withRequestsMadeViaParent. The child TransferCache evalu

  • Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.30, 21.2.22, and 22.1.4, Angular server-side rendering (SSR) in @angular/platform-server serializes ProcessingInstruction DOM nodes inside fallback raw-content elements without escaping matching ancestor closing tags. ProcessingInstruction data escaped g

  • Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.30, 21.2.22, and 22.1.4, Angular server-side rendering (SSR) in @angular/platform-server serializes untrusted input inside template content nested in fallback raw-content elements such as noscript, iframe, noembed, and noframes. The Domino serializer's f

  • Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.28, 21.2.20, and 22.1.0, Angular's compiler and runtime in @angular/core and @angular/compiler could omit or select an incorrect sanitizer for security-sensitive directive host bindings because SecurityContext was derived from the declaring directive or

  • Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.30, 21.2.22, and 22.1.4, Angular Server-Side Rendering in @angular/platform-server processes user-controlled resource or request URLs through HttpClient after application code validates them with WHATWG URL parsing. The resolveUrl and parseUrl utilities

  • Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.27, 21.2.19, and 22.0.1, the Angular compiler i18n pipeline permits i18n-onerror and other i18n-on event-handler attributes, allowing a lower-trust translation file to replace a static handler with executable JavaScript. This issue is fixed in versions 2

  • Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.27, 21.2.19, and 22.0.7, a Cross-Site Scripting (XSS) vulnerability exists in @angular/platform-server's DOM emulation dependency (domino) when serializing the content of fallback raw-content elements (<iframe>, <noembed>, <noframes>, and <noscript>). Th

  • Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.27, 21.2.19, and 22.0.2, HttpTransferCache comma-joins repeated request parameters, allowing semantically distinct HttpClient requests to use the same transfer-cache key and reuse a wrong backend response. This issue is fixed in versions 20.3.27, 21.2.19

About this page

This page gathers every public program listed under google.com and the companies Google owns: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test. Ownership comes from settled, public acquisitions, or from a program's own text naming Google.

Something wrong or missing? Report a correction.