CVE-2026-73514: PostGIS address_standardizer · Out-of-bounds Write
Affects PostGIS address_standardizerSource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 11 Nov 2026, 23:24 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.7 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 8.8 |
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostGISaddress_standardizer | Affected
| Fixed in– |
GitHubaddress_standardizerpkg:github/address_standardizerOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix for this vulnerability is available in the commit identified as 423570b. Users of the address_standardizer extension in PostGIS should update to a version that includes this fix. Since this is not a cloud service, manual patching or upgrading is required to remediate the vulnerability.
Description
CVE-2026-73514 is an out-of-bounds write vulnerability in the address_standardizer extension for PostGIS up to version 3.7.0. It allows a database user who can supply relation names to the standardize_address() function to cause memory corruption by providing a malicious rules table entry with an oversized classification Type value. This value is used without proper bounds checking, leading to an out-of-bounds write in an internal output-link table.
References
- mehmetince.net/part-1-6-systemic-risks-in-the-managed-postgresql-industry-extension-risks-are-real-exploiting-postgis-memory-corruption-bug-at-neondb-supabase-and-many-more/ (opens in a new tab)
- github.com/postgis/address_standardizer/pull/3 (opens in a new tab)
- github.com/postgis/address_standardizer/pull/4 (opens in a new tab)
- github.com/postgis/address_standardizer/commit/423570b0dbf6cd9f6fc36de28a636e7b6e9aa8aa (opens in a new tab)
- vulncheck.com/advisories/postgis-address-standardizer-out-of-bounds-write-via-standardize-address (opens in a new tab)