# CVE-2026-7428: Insecure default administrative credentials in AlloyDB for PostgreSQL

> Remote attackers can gain full administrative access to AlloyDB clusters created via Terraform or REST API due to insecure default credentials.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-fmcg-2r5c-wmhp

## What is CVE-2026-7428?

CVE-2026-7428 is a critical vulnerability in Google Cloud AlloyDB for PostgreSQL, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-1392 (Use of Default Credentials)

## Which versions are affected by CVE-2026-7428?


## How do I fix CVE-2026-7428?

No fix has been published for CVE-2026-7428 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7428 being exploited?

There is no known exploitation of CVE-2026-7428 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7428 and fix it if it is affected.

What it is: CVE-2026-7428 is a critical vulnerability in Google Cloud AlloyDB for PostgreSQL, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7428 in the wild and no public exploit code.

Affected product: Google Cloud AlloyDB for PostgreSQL. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7428/ (Markdown: https://insights.sbomify.com/CVE-2026-7428/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7428
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7428
- OSV: https://osv.dev/vulnerability/CVE-2026-7428

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7428/
Summaries are generated and may contain mistakes; the official description above is the record.