CVE-2026-73514

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. A secondary CVSS source baseline 8.8; sources differ by 0.0.

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

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.8HIGHmedium confidence
EG Risk
56
EG Risk 56/100CISA SSVC

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%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 13, 2026

Last Modified

September 24, 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 19× in last 7d / 94× 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.

Showing the most recent 100 of 187 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 22:19 UTCGHSA enrichment
  3. 2026-10-04 08:12 UTCGHSA enrichment
  4. 2026-10-03 19:48 UTCEG score recompute
  5. 2026-10-03 19:48 UTCGHSA enrichment
  6. 2026-10-03 14:26 UTCEPSS rescore
  7. 2026-10-02 19:47 UTCEG score recompute
  8. 2026-10-02 19:47 UTCGHSA enrichment
  9. 2026-10-02 07:33 UTCEG score recompute
  10. 2026-10-02 07:33 UTCGHSA enrichment
  11. 2026-10-01 19:50 UTCEPSS rescore
  12. 2026-10-01 10:01 UTCGHSA enrichment
  13. 2026-09-30 21:46 UTCEG score recompute
  14. 2026-09-30 21:46 UTCGHSA enrichment
  15. 2026-09-29 15:24 UTCEPSS rescore
  16. 2026-09-29 03:54 UTCEG score recompute
  17. 2026-09-29 03:54 UTCGHSA enrichment
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-28 13:00 UTCGHSA enrichment
  20. 2026-09-28 00:46 UTCEG score recompute
  21. 2026-09-28 00:46 UTCGHSA enrichment
  22. 2026-09-27 13:48 UTCEPSS rescore
  23. 2026-09-27 09:44 UTCEG score recompute
  24. 2026-09-27 09:44 UTCGHSA enrichment
  25. 2026-09-26 15:59 UTCEPSS rescore
Show 75 more
  1. 2026-09-25 08:32 UTCGHSA enrichment
  2. 2026-09-24 20:17 UTCEG score recompute
  3. 2026-09-24 20:17 UTCGHSA enrichment
  4. 2026-09-24 09:44 UTCGHSA enrichment
  5. 2026-09-23 21:30 UTCEG score recompute
  6. 2026-09-23 21:30 UTCGHSA enrichment
  7. 2026-09-23 17:54 UTCEPSS rescore
  8. 2026-09-23 09:16 UTCGHSA enrichment
  9. 2026-09-22 21:00 UTCEG score recompute
  10. 2026-09-22 21:00 UTCGHSA enrichment
  11. 2026-09-22 08:11 UTCEG score recompute
  12. 2026-09-22 08:11 UTCGHSA enrichment
  13. 2026-09-21 21:09 UTCEPSS rescore
  14. 2026-09-21 19:54 UTCGHSA enrichment
  15. 2026-09-21 04:16 UTCEG score recompute
  16. 2026-09-21 04:16 UTCGHSA enrichment
  17. 2026-09-20 20:16 UTCEPSS rescore
  18. 2026-09-20 15:56 UTCGHSA enrichment
  19. 2026-09-20 01:33 UTCEG score recompute
  20. 2026-09-20 01:33 UTCGHSA enrichment
  21. 2026-09-19 13:19 UTCGHSA enrichment
  22. 2026-09-19 01:05 UTCEG score recompute
  23. 2026-09-19 01:05 UTCGHSA enrichment
  24. 2026-09-18 19:28 UTCEPSS rescore
  25. 2026-09-18 12:49 UTCGHSA enrichment
  26. 2026-09-18 00:29 UTCEG score recompute
  27. 2026-09-18 00:29 UTCGHSA enrichment
  28. 2026-09-17 12:14 UTCGHSA enrichment
  29. 2026-09-16 23:59 UTCEG score recompute
  30. 2026-09-16 23:59 UTCGHSA enrichment
  31. 2026-09-16 14:08 UTCEPSS rescore
  32. 2026-09-16 10:28 UTCEG score recompute
  33. 2026-09-16 10:28 UTCGHSA enrichment
  34. 2026-09-16 05:15 UTCEPSS rescore
  35. 2026-09-15 21:54 UTCGHSA enrichment
  36. 2026-09-15 09:04 UTCEG score recompute
  37. 2026-09-15 09:04 UTCGHSA enrichment
  38. 2026-09-15 03:12 UTCEPSS rescore
  39. 2026-09-14 20:49 UTCGHSA enrichment
  40. 2026-09-14 08:26 UTCGHSA enrichment
  41. 2026-09-13 20:11 UTCEG score recompute
  42. 2026-09-13 20:11 UTCGHSA enrichment
  43. 2026-09-13 07:56 UTCGHSA enrichment
  44. 2026-09-12 19:42 UTCEG score recompute
  45. 2026-09-12 19:42 UTCGHSA enrichment
  46. 2026-09-12 15:02 UTCEPSS rescore
  47. 2026-09-12 07:28 UTCGHSA enrichment
  48. 2026-09-11 19:13 UTCEG score recompute
  49. 2026-09-11 19:13 UTCGHSA enrichment
  50. 2026-09-11 14:53 UTCEPSS rescore
  51. 2026-09-11 06:48 UTCGHSA enrichment
  52. 2026-09-10 18:33 UTCEG score recompute
  53. 2026-09-10 18:33 UTCGHSA enrichment
  54. 2026-09-10 09:35 UTCEPSS rescore
  55. 2026-09-10 06:14 UTCGHSA enrichment
  56. 2026-09-09 17:44 UTCGHSA enrichment
  57. 2026-09-09 04:57 UTCEG score recompute
  58. 2026-09-09 04:57 UTCGHSA enrichment
  59. 2026-09-08 22:01 UTCEPSS rescore
  60. 2026-09-08 06:19 UTCGHSA enrichment
  61. 2026-09-07 17:58 UTCEG score recompute
  62. 2026-09-07 17:58 UTCGHSA enrichment
  63. 2026-09-07 05:44 UTCEG score recompute
  64. 2026-09-07 05:44 UTCGHSA enrichment
  65. 2026-09-06 13:48 UTCEPSS rescore
  66. 2026-09-06 13:31 UTCGHSA enrichment
  67. 2026-09-06 01:17 UTCEG score recompute
  68. 2026-09-06 01:16 UTCGHSA enrichment
  69. 2026-09-05 12:51 UTCGHSA enrichment
  70. 2026-09-05 00:30 UTCEG score recompute
  71. 2026-09-05 00:30 UTCGHSA enrichment
  72. 2026-09-04 06:16 UTCEG score recompute
  73. 2026-09-04 06:15 UTCGHSA enrichment
  74. 2026-09-04 05:07 UTCEPSS rescore
  75. 2026-09-03 16:13 UTCGHSA enrichment

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 on August 13, 2026, with the most recent update on September 24, 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.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73514?
CVE-2026-73514 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73514?
An upstream fix for CVE-2026-73514 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-73514 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs