๐Ÿ” CVE Alert

CVE-2026-73514

HIGH 8.8

PostGIS address_standardizer Out-of-Bounds Write via standardize_address()

CVSS Score
8.8
EPSS Score
0.0%
EPSS Percentile
0th

The address_standardizer extension for PostGIS through 3.7.0, fixed in commit 423570b, contains an out-of-bounds write vulnerability that allows a database user with the ability to supply caller-controlled relation names to standardize_address() to trigger memory corruption by providing a rules table with a classification Type value exceeding the fixed class range. Attackers can craft a malicious rules table entry with an oversized rule type value that is used without bounds checking as an index into an internal output-link table, resulting in an out-of-bounds write.

CWE CWE-787
Vendor postgis
Product address_standardizer
Published Aug 13, 2026
Last Updated Aug 13, 2026
Stay Ahead of the Next One

Get instant alerts for postgis address_standardizer

Be the first to know when new high vulnerabilities affecting postgis address_standardizer are published โ€” delivered to Slack, Telegram or Discord.

Get Free Alerts โ†’ Free ยท No credit card ยท 60 sec setup

CVSS v3 Breakdown

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Affected Versions

PostGIS / address_standardizer
0 < 423570b0dbf6cd9f6fc36de28a636e7b6e9aa8aa

References

NVD โ†— CVE.org โ†— EPSS Data โ†—
mehmetince.net: https://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/ github.com: https://github.com/postgis/address_standardizer/pull/3 github.com: https://github.com/postgis/address_standardizer/pull/4 github.com: https://github.com/postgis/address_standardizer/commit/423570b0dbf6cd9f6fc36de28a636e7b6e9aa8aa vulncheck.com: https://www.vulncheck.com/advisories/postgis-address-standardizer-out-of-bounds-write-via-standardize-address

Credits

Mehmet Ince (@mdisec)