Administrative takeover via insecure default password
Published May 12, 2026 · Updated May 12, 2026
Use of default credentials in Google Cloud AlloyDB for PostgreSQL before 2025-11-03 allows remote attackers to gain administrative access. Terraform and REST API cluster creation accepted an unspecified initial user or password and assigned an insecure default instead of locking the postgres role. Only clusters created through those interfaces were exposed, and exploitation required network access to the cluster, granting full control over database data and operations.
Summary
What happened
Use of default credentials in Google Cloud AlloyDB for PostgreSQL before 2025-11-03 allows remote attackers to gain administrative access. Terraform and REST API cluster creation accepted an unspecified initial user or password and assigned an insecure default instead of locking the postgres role. Only clusters created through those interfaces were exposed, and exploitation required network access to the cluster, granting full control over database data and operations.
The record
- CVE
- CVE-2026-7428
- Published
- May 12, 2026
- Updated
- May 12, 2026
- Vendor
- Go standard library
- Product
- AlloyDB for PostgreSQL
- Classifications
- CWE-1392, CAPEC-70, T1078.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2026CVE publishedPublication date reported by the CVE source.
- May 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2025-11-03
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo