PostGIS before 3.7.0beta2 contains an out-of-bounds read vulnerability that allows attackers to cause memory disclosure or a server crash by supplying a malformed FlatGeobuf buffer. The FlatGeobuf property metadata decoder verifies that a string length field is present but fails to verify that the subsequent string body is contained within the supplied buffer before materializing it into a SQL-visible value, enabling memory disclosure or denial of service.
CVE-2026-73515
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. the CNA's CVSS baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 52(Track*)EG Risk 52/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 computedSeverity81% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 14, 2026
Advisory Details (3)
Auto-updated Aug 13, 2026PostGIS < 3.7.0beta2 Out-of-Bounds Read via FlatGeobuf Buffer | Advisories | VulnCheck
https://www.vulncheck.com/advisories/postgis-0beta2-out-of-bounds-read-via-flatgeobuf-bufferPart 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-73515(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 / 38× 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.
- 2026-08-21 08:12 UTCEG score recompute
- 2026-08-21 08:12 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 20:03 UTCGHSA enrichment
- 2026-08-20 07:54 UTCGHSA enrichment
- 2026-08-19 19:46 UTCEG score recompute
- 2026-08-19 19:46 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 07:36 UTCGHSA enrichment
- 2026-08-18 19:28 UTCEG score recompute
- 2026-08-18 19:28 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 07:19 UTCGHSA enrichment
- 2026-08-17 19:11 UTCEG score recompute
- 2026-08-17 19:10 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 05:50 UTCGHSA enrichment
- 2026-08-16 17:42 UTCEG score recompute
- 2026-08-16 17:42 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 05:33 UTCEG score recompute
- 2026-08-16 05:33 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
Show 13 moreShow fewer
- 2026-08-15 17:25 UTCGHSA enrichment
- 2026-08-15 05:16 UTCEG score recompute
- 2026-08-15 05:16 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 17:07 UTCEG score recompute
- 2026-08-14 17:07 UTCGHSA enrichment
- 2026-08-14 06:27 UTCEG score recompute
- 2026-08-14 06:27 UTCGHSA enrichment
- 2026-08-13 18:18 UTCEG score recompute
- 2026-08-13 17:27 UTCEG score recompute
- 2026-08-13 16:25 UTCEG score recompute
- 2026-08-13 15:57 UTCEG score recompute
- 2026-08-13 15:56 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-125
- CVE-2013-0767EG 10.0EPSS p93HIGH
- CVE-2009-2523EG 10.0EPSS p98HIGH
- CVE-2014-2898EG 9.8CRITICAL
- CVE-2014-2897EG 9.8CRITICAL
- CVE-2014-2896EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS p96CRITICAL
- CVE-2014-1522EG 9.3EPSS p92HIGH
- CVE-2013-0779EG 9.3EPSS p92HIGH
- CVE-2013-0778EG 9.3EPSS p90HIGH
- CVE-2012-3995EG 9.3EPSS p92HIGH
Frequently asked(5)
What is CVE-2026-73515?
When was CVE-2026-73515 disclosed?
Is CVE-2026-73515 actively exploited?
What is the CVSS score of CVE-2026-73515?
How do I remediate CVE-2026-73515?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-73515
Is Your Infrastructure Affected by CVE-2026-73515?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.