Is CVE-2026-7428 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-7428 being exploited in the wild.

How severe is CVE-2026-7428?

Informational severity, with a CVSS score of 9.2, published 12 May 2026.

Which products and versions are affected?

Google AlloyDB Prior to 2025-11-03.

Is there a fix for CVE-2026-7428?

A patch was published on 2025-11-03: Date by which the insecure default behavior was remediated Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-7428 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-7428?

Check whether you run Google AlloyDB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-7428: Google Cloud AlloyDB insecure default password via Terraform and REST API

CVE-2026-7428 · Severity: info · CVSS 9.2 · Published 2026-05-12

Google Cloud AlloyDB for PostgreSQL is a fully managed, PostgreSQL-compatible database service. A security issue was identified where database clusters created via Terraform or the REST API prior to November 2025 could have been configured with an insecure default password. If exploited, a remote attacker with network access to the database could gain full administrative control, potentially leading to the theft, modification, or deletion of sensitive customer data.

Vendors: Google.

Quick answers

Is CVE-2026-7428 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-7428 being exploited in the wild.
How severe is CVE-2026-7428?: Informational severity, with a CVSS score of 9.2, published 12 May 2026.
Which products and versions are affected?: Google AlloyDB Prior to 2025-11-03.
Is there a fix for CVE-2026-7428?: A patch was published on 2025-11-03: Date by which the insecure default behavior was remediated Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-7428 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-7428?: Check whether you run Google AlloyDB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability in the provisioning process of Google Cloud AlloyDB for PostgreSQL allowed for the creation of database clusters with insecure default credentials (CWE-1392). The issue specifically affected clusters created using Terraform or the direct REST API; other interfaces, such as the Google Cloud Console, reportedly blocked this behavior. An attacker with network reachability to the database instance could use these default credentials to gain full administrative (superuser) access to the PostgreSQL environment. Google has since updated the service so that if a password is not specified during creation, the 'postgres' role is created in a locked state with a null password.

Affected products

Google Cloud AlloyDB for PostgreSQL Prior to 2025-11-03

Timeline

2025-11-03: patched: Date by which the insecure default behavior was remediated
2026-04-28: advisory: Release notes updated regarding locked postgres role behavior
2026-05-12: disclosed: CVE-2026-7428 published

References

https://docs.cloud.google.com/alloydb/docs/release-notes

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.