CVE-2026-73514

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
56(Track*)
EG Risk 56/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 14, 2026

Advisory Details (5)

Auto-updated Aug 13, 2026
⚠️ Active exploitation confirmed. Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic

PostGIS address_standardizer Out-of-Bounds Write via standardize_address() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/postgis-address-standardizer-out-of-bounds-write-via-standardize-address
github_commit

commit 423570b0dbf6 (postgis/address_standardizer)

Fix landed in postgis/address_standardizer commit 423570b0dbf6 — awaiting tagged release

https://github.com/postgis/address_standardizer/commit/423570b0dbf6cd9f6fc36de28a636e7b6e9aa8aa
github_pr

Harden scanner and rule parsing bounds

Fix merged in postgis/address_standardizer PR #4 on 2026-08-09 — awaiting tagged release

https://github.com/postgis/address_standardizer/pull/4
github_pr

Fix exploited oob write Type rule field

Upstream fix in progress (PR #3 · postgis/address_standardizer, state=closed)

https://github.com/postgis/address_standardizer/pull/3
generic🔴 Active Exploitation

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 - Mehmet Ince @mdisec - Vulnerability Researcher | Building security products | Security Advisor | Amateur Muay Thai fighter

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/

Vendor Advisories for CVE-2026-73514(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 31× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 16:12 UTCGHSA enrichment
  3. 2026-08-20 03:55 UTCEG score recompute
  4. 2026-08-20 03:55 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-19 15:40 UTCGHSA enrichment
  7. 2026-08-19 03:26 UTCGHSA enrichment
  8. 2026-08-18 15:12 UTCEG score recompute
  9. 2026-08-18 15:12 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 02:52 UTCGHSA enrichment
  13. 2026-08-17 14:38 UTCEG score recompute
  14. 2026-08-17 14:38 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 02:24 UTCEG score recompute
  17. 2026-08-17 02:24 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 14:10 UTCEG score recompute
  21. 2026-08-16 14:10 UTCGHSA enrichment
  22. 2026-08-16 02:15 UTCEPSS rescore
  23. 2026-08-16 01:56 UTCGHSA enrichment
  24. 2026-08-15 13:42 UTCEG score recompute
  25. 2026-08-15 13:42 UTCGHSA enrichment
Show 11 more
  1. 2026-08-15 01:31 UTCEPSS rescore
  2. 2026-08-15 01:27 UTCGHSA enrichment
  3. 2026-08-14 13:14 UTCEG score recompute
  4. 2026-08-14 13:14 UTCGHSA enrichment
  5. 2026-08-14 06:32 UTCEG score recompute
  6. 2026-08-14 06:32 UTCGHSA enrichment
  7. 2026-08-13 18:18 UTCEG score recompute
  8. 2026-08-13 17:47 UTCEG score recompute
  9. 2026-08-13 16:25 UTCEG score recompute
  10. 2026-08-13 15:57 UTCEG score recompute
  11. 2026-08-13 15:56 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73514?
CVE-2026-73514 is a high vulnerability published on August 13, 2026. The addressstandardizer 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 standardizeaddress() to trigger memory corruption by providing a rules table…
When was CVE-2026-73514 disclosed?
CVE-2026-73514 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73514 actively exploited?
CVE-2026-73514 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.8% of all scored CVEs.
What is the CVSS score of CVE-2026-73514?
CVE-2026-73514 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-73514?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73514, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73514

Explore →

Is Your Infrastructure Affected by CVE-2026-73514?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs