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.
Exploitation required network access to the AlloyDB cluster and was limited to Terraform or the REST API, as other clients blocked it.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
This vulnerability was patched on November 3, 2025. Impacted instances have been proactively remediated, and no customer action is needed.
Workaround
No workaround given by the vendor.
References
History
Tue, 12 May 2026 09:30:00 +0000
| 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
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GoogleCloud
Published:
Updated: 2026-05-12T09:16:35.151Z
Reserved: 2026-04-29T14:38:05.602Z
Link: CVE-2026-7428
No data.
Status : Received
Published: 2026-05-12T10:16:48.490
Modified: 2026-05-12T10:16:48.490
Link: CVE-2026-7428
No data.
OpenCVE Enrichment
No data.
Weaknesses