Unauthorized access through stored credentials in Looker Studio
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Google Cloud | Looker Studio | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Cloud Looker | — | |
| Looker | — |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.274% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google cloud Looker Google looker |
|
| Vendors & Products |
Google
Google cloud Looker Google looker |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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 due to the stored credentials attached to the report. This vulnerability was patched on 21 July 2025, and no customer action is needed. | |
| Title | Unauthorized access through stored credentials in Looker Studio | |
| Weaknesses | CWE-269 | |
| References |
| |
| Metrics |
cvssV4_0
|