CVE-2026-73514
Out‑of‑bounds write in PostGIS address_standardizer leading to memory corruption.
Is CVE-2026-73514 being exploited?
Not confirmed. CVE-2026-73514 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.61% probability of exploitation in the next 30 days.
How severe is CVE-2026-73514?
CVE-2026-73514 is rated High with a CVSS score of 8.7. 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-73514?
Yes. A fix has been recorded for CVE-2026-73514. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73514 affect?
CVE-2026-73514 affects PostGIS address_standardizer extension <= 3.7.0, standardize_address() function, PostgreSQL databases with PostGIS installed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73514?
Upgrade PostGIS to include commit 423570b or later; restrict access to the function/tables.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted rules table causes OOB write in standardize_address(), leading to DB crash or possible arbitrary code execution; attacker needs ability to supply relation names.
Patch when possible
- affected< 423570b0dbf6cd9f6fc36de28a636e7b6e9aa8aa
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.