PostGIS up to 3.7.0 address_standardizer standardize_address out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.9 | $0-$5k | 2.07 |
Summary
A vulnerability was found in PostGIS up to 3.7.0 and classified as very critical. Affected is the function standardize_address of the component address_standardizer. The manipulation results in out-of-bounds write.
This vulnerability is reported as CVE-2026-73514. The attack can be launched remotely. Moreover, an exploit is present.
Details
A vulnerability was found in PostGIS up to 3.7.0. It has been classified as very critical. Affected is the function standardize_address of the component address_standardizer. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. CWE is classifying the issue as CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at mehmetince.net. This vulnerability is traded as CVE-2026-73514 since 08/12/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details and a exploit are known. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 08/13/2026).
The exploit is shared for download at mehmetince.net. It is declared as proof-of-concept.
Applying the patch 423570b is able to eliminate this problem.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 8.9
VulDB Base Score: 9.9
VulDB Temp Score: 8.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Out-of-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: 423570b
Timeline
08/12/2026 CVE reserved08/13/2026 Advisory disclosed
08/13/2026 VulDB entry created
08/13/2026 VulDB entry last update
Sources
Advisory: mehmetince.netStatus: Confirmed
CVE: CVE-2026-73514 (🔒)
GCVE (CVE): GCVE-0-2026-73514
GCVE (VulDB): GCVE-100-389652
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/13/2026 18:14Changes: 08/13/2026 18:14 (57)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.