Insecure default administrative credentials in AlloyDB for PostgreSQL
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 | AlloyDB for PostgreSQL | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Google Cloud | Alloydb For Postgresql |
|
Vendor Solution
This vulnerability was patched on November 3, 2025. Impacted instances have been proactively remediated, and no customer action is needed.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.239% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google Cloud
Google Cloud alloydb For Postgresql |
|
| Vendors & Products |
Google Cloud
Google Cloud alloydb For Postgresql |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Prior to 2025-11-03, well-intended users of Terraform or REST API for Google Cloud AlloyDB for PostgreSQL could have created clusters with an insecure default password which could have been exploited by a remote attacker to gain full administrative access to the database. Exploitation required network access to the AlloyDB cluster and was limited to Terraform or the REST API, as other clients blocked it. | |
| Title | Insecure default administrative credentials in AlloyDB for PostgreSQL | |
| Weaknesses | CWE-1392 | |
| References |
| |
| Metrics |
cvssV4_0
|