Google Cloud vulnerabilities
We track 56 vulnerabilities in Google Cloud products across 37 products. 56 are rated high or critical, and none are known to be exploited. The most recent was published on October 30, 2026.
Latest Google Cloud vulnerabilities
- 7.6 High severity
Apigee-X: Improper Privilege Management
A vulnerability in Apigee-X allowed an attacker to gain unauthorized read and write access to Apigee Analytics (AX) data and access logs belonging to other Apigee customer organizations. Apigee-X was found to be vulnerable. This vulnerability was patched in ve
- 8.7 High severity
Apigee hybrid Javacallout policy: Improper Control of Dynamically-Managed Code Resources
A vulnerability exists in Google Apigee's JavaCallout policy https://docs.apigee.com/api-platform/reference/policies/java-callout-policy that allows for remote code execution. It is possible for a user to write a JavaCallout that injected a malicious object in
- 7.5 High severity
Looker: Improper Neutralization of Special Elements used in an OS Command
A Looker user with a Developer role could cause Looker to execute a malicious command, due to insecure processing of Teradata driver parameters. Looker-hosted and Self-hosted were found to be vulnerable. This issue has already been mitigated for Looker-hosted
- 7.7 High severity
A Looker user with Developer role could create a database connection using Denodo driver and…
A Looker user with Developer role could create a database connection using Denodo driver and, by manipulating LookML, cause Looker to execute a malicious command. Looker-hosted and Self-hosted were found to be vulnerable. This issue has already been mitigated
- 7.7 High severity
A Looker user with a Developer role could create a database connection using IBM DB2 driver…
A Looker user with a Developer role could create a database connection using IBM DB2 driver and, by manipulating LookML, cause Looker to execute a malicious command, due to inadequate filtering of the driver's parameters. Looker-hosted and Self-hosted were fou
- 7.3 High severity
Looker: Improper Neutralization of Input During Web Page Generation
An attacker with viewer permissions in Looker could craft a malicious URL that, when opened by a Looker admin, would execute an attacker-supplied script. Exploitation required at least one Looker extension installed on the instance. Looker-hosted and Self-host
- 9.2 Critical severity
Looker: Authentication Bypass by Spoofing
An attacker could take over a Looker account in a Looker instance configured with OIDC authentication, due to email address string normalization.Looker-hosted and Self-hosted were found to be vulnerable. This issue has already been mitigated for Looker-hosted.
- 7.1 High severity
Looker: Concurrent Execution using Shared Resource with Improper Synchronization
An attacker with a Looker Developer role could manipulate a LookML project to exploit a race condition during Git directory deletion, leading to arbitrary command execution on the Looker instance. Looker-hosted and Self-hosted were found to be vulnerable. This
- 7.7 High severity
Looker Studio: Improper Privilege Management
An improper privilege management vulnerability was found in Looker Studio. It impacted all JDBC-based connectors. A Looker Studio user with report view access could make a copy of the report and execute arbitrary SQL that would run on the data source database
- 7.3 High severity
Looker Studio: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability was discovered in Looker Studio that allowed for data exfiltration from BigQuery data sources. By creating a malicious report with native functions enabled, and having the victim access the report, an attacker could execute inject
- 7.6 High severity
Looker Studio: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability was found in Looker Studio. A Looker Studio user with report view access could inject malicious SQL that would execute with the report owner's permissions. The vulnerability affected to reports with BigQuery as the data source. Th
- 7.1 High severity
Looker: Improper Neutralization of Special Elements used in a Command
A Command Injection vulnerability, resulting from improper file path sanitization (Directory Traversal) in Looker allows an attacker with Developer permission to execute arbitrary shell commands when a user is deleted on the host system. Looker-hosted and Self
- 8.7 High severity
Google SecOps SOAR: Improper Limitation of a Pathname to a Restricted Directory
A Path Traversal vulnerability in the archive extraction component in Google SecOps SOAR Server (versions 6.3.54.0, 6.3.53.2, and all prior versions) allows an authenticated attacker with permissions to import Use Cases to achieve Remote Code Execution (RCE) v
- 10.0 Critical severity
Dataform: Improper Limitation of a Pathname to a Restricted Directory
A path traversal vulnerability in the NPM package installation process of Google Cloud Dataform allows a remote attacker to read and write files in other customers' repositories via a maliciously crafted package.json file.
- 7.5 High severity
Classic Application Load Balancer: Inconsistent Interpretation of HTTP Requests
A request smuggling vulnerability existed in the Google Cloud Classic Application Load Balancer due to improper handling of chunked-encoded HTTP requests. This allowed attackers to craft requests that could be misinterpreted by backend servers. The issue was f
- 10.0 Critical severity
Application Integration: Inclusion of Functionality from Untrusted Control Sphere
Sandbox escape in the JavaScript Task feature of Google Cloud Application Integration allows an actor to execute arbitrary unsandboxed code via crafted JavaScript code executed by the Rhino engine. Effective January 24, 2025, Application Integration will no lo