# CVE-2026-73514: PostGIS address_standardizer Out-of-Bounds Write via standardize_address()

> A database user can trigger an out-of-bounds write in PostGIS address_standardizer via a malicious rules table, potentially leading to memory corruption or code execution.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-7xxg-v5x5-6wjr

## What is CVE-2026-73514?

CVE-2026-73514 is a high-severity memory corruption vulnerability in PostGIS address_standardizer, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-73514?


## How do I fix CVE-2026-73514?

No fix has been published for CVE-2026-73514 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73514 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73514 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73514 and fix it if it is affected.

What it is: CVE-2026-73514 is a high-severity memory corruption vulnerability in PostGIS address_standardizer, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73514 exists.

Affected product: PostGIS address_standardizer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73514/ (Markdown: https://insights.sbomify.com/CVE-2026-73514/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73514
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73514
- OSV: https://osv.dev/vulnerability/CVE-2026-73514

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73514/
Summaries are generated and may contain mistakes; the official description above is the record.