CVE-2026-7428
Insecure default password in AlloyDB via Terraform/REST API allows remote admin access.
Is CVE-2026-7428 being exploited?
Not confirmed. CVE-2026-7428 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-7428?
CVE-2026-7428 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-7428?
Yes. A fix has been recorded for CVE-2026-7428. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-7428 affect?
CVE-2026-7428 affects Google Cloud AlloyDB for PostgreSQL. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-7428?
Rotate credentials; disable insecure defaults; review Terraform/REST access; patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker with network access can gain full admin DB access via insecure default passwords created through Terraform/REST API.
Immediate action required
- affected< 2025-11-03
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.