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. A secondary CVSS source baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.1
- EG Score
- 8.1HIGHmedium confidence
- EG Risk
- 52EG Risk 52/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 computedSeverity81% × 45%Exploitation40% × 40%Automatability0% × 15%CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.6%
- EPSS %ILE
- 45th
- KEV
- Not listed
CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
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 (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(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:67848Red Hat Product SecurityHigh
Red Hat Security Advisory: postgresql:18 security update
- RHSA-2026:67491Red Hat Product SecurityHigh
Red Hat Security Advisory: postgresql:16 security update
- GHSA-qv7r-wgc7-6mc6GitHub Security AdvisoriesHigh
PostGIS before 3.7.0beta2 contains an out-of-bounds read vulnerability that allows attackers to...
Patch Availability(4)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | postgresql:18-9080020260914093252.rhel9 | 2026-09-16 | redhat |
| redhat | postgresql:16-9080020260907191505.rhel9 | 2026-09-15 | redhat |
| redhat | postgresql18-postgis-0:3.5.3-1.el10_2.1 | 2026-09-14 | redhat |
| redhat | postgresql16-postgis-0:3.5.3-4.el10_2.1 | 2026-09-09 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgis | 3.3.2+dfsg-1 ... 3.7.0~rc2+dfsg-1~exp1 (67 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgis | 3.5.2+dfsg-1 ... 3.7.0~rc2+dfsg-1~exp1 (23 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgis | 3.5.2+dfsg-1 ... 3.7.0~rc2+dfsg-1~exp1 (23 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 26× in last 7d / 135× 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 229 total refreshes for this CVE.
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-04 22:19 UTCVendor advisory
- 2026-10-04 22:19 UTCGHSA enrichment
- 2026-10-04 08:12 UTCVendor advisory
- 2026-10-04 08:12 UTCGHSA enrichment
- 2026-10-03 19:48 UTCEG score recompute
- 2026-10-03 19:48 UTCVendor advisory
- 2026-10-03 19:48 UTCGHSA enrichment
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 19:42 UTCEG score recompute
- 2026-10-02 19:42 UTCVendor advisory
- 2026-10-02 19:42 UTCGHSA enrichment
- 2026-10-02 07:33 UTCEG score recompute
- 2026-10-02 07:33 UTCVendor advisory
- 2026-10-02 07:33 UTCGHSA enrichment
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-10-01 09:55 UTCVendor advisory
- 2026-10-01 09:55 UTCGHSA enrichment
- 2026-09-30 21:46 UTCEG score recompute
- 2026-09-30 21:46 UTCVendor advisory
- 2026-09-30 21:46 UTCGHSA enrichment
- 2026-09-29 15:24 UTCEPSS rescore
- 2026-09-29 03:54 UTCEG score recompute
- 2026-09-29 03:54 UTCVendor advisory
- 2026-09-29 03:54 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-28 13:52 UTCEPSS rescore
- 2026-09-28 12:55 UTCVendor advisory
- 2026-09-28 12:55 UTCGHSA enrichment
- 2026-09-28 00:46 UTCEG score recompute
- 2026-09-28 00:46 UTCVendor advisory
- 2026-09-28 00:46 UTCGHSA enrichment
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-27 09:44 UTCEG score recompute
- 2026-09-27 09:44 UTCVendor advisory
- 2026-09-27 09:44 UTCGHSA enrichment
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-25 08:32 UTCVendor advisory
- 2026-09-25 08:32 UTCGHSA enrichment
- 2026-09-24 20:17 UTCEG score recompute
- 2026-09-24 20:17 UTCVendor advisory
- 2026-09-24 20:17 UTCGHSA enrichment
- 2026-09-24 09:33 UTCVendor advisory
- 2026-09-24 09:33 UTCGHSA enrichment
- 2026-09-23 21:17 UTCEG score recompute
- 2026-09-23 21:17 UTCVendor advisory
- 2026-09-23 21:17 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 09:09 UTCVendor advisory
- 2026-09-23 09:09 UTCGHSA enrichment
- 2026-09-22 21:00 UTCEG score recompute
- 2026-09-22 21:00 UTCVendor advisory
- 2026-09-22 21:00 UTCGHSA enrichment
- 2026-09-22 08:11 UTCEG score recompute
- 2026-09-22 08:11 UTCVendor advisory
- 2026-09-22 08:11 UTCGHSA enrichment
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-21 19:54 UTCVendor advisory
- 2026-09-21 19:54 UTCGHSA enrichment
- 2026-09-21 04:16 UTCEG score recompute
- 2026-09-21 04:16 UTCVendor advisory
- 2026-09-21 04:16 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 15:56 UTCVendor advisory
- 2026-09-20 15:56 UTCGHSA enrichment
- 2026-09-20 01:17 UTCEG score recompute
- 2026-09-20 01:17 UTCVendor advisory
- 2026-09-20 01:17 UTCGHSA enrichment
- 2026-09-19 13:08 UTCVendor advisory
- 2026-09-19 13:08 UTCGHSA enrichment
- 2026-09-19 00:59 UTCEG score recompute
- 2026-09-19 00:59 UTCVendor advisory
- 2026-09-19 00:59 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 12:49 UTCVendor advisory
- 2026-09-18 12:49 UTCGHSA enrichment
- 2026-09-18 00:29 UTCEG score recompute
- 2026-09-18 00:29 UTCVendor advisory
- 2026-09-18 00:29 UTCGHSA enrichment
- 2026-09-17 12:08 UTCVendor advisory
- 2026-09-17 12:08 UTCGHSA enrichment
- 2026-09-16 23:59 UTCEG score recompute
- 2026-09-16 23:59 UTCVendor advisory
- 2026-09-16 23:59 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 10:28 UTCEG score recompute
- 2026-09-16 10:28 UTCVendor advisory
- 2026-09-16 10:28 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 21:55 UTCVendor advisory
- 2026-09-15 21:54 UTCGHSA enrichment
- 2026-09-15 08:58 UTCEG score recompute
- 2026-09-15 08:58 UTCVendor advisory
- 2026-09-15 08:58 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 20:49 UTCVendor advisory
- 2026-09-14 20:49 UTCGHSA enrichment
- 2026-09-14 07:15 UTCVendor advisory
- 2026-09-14 07:15 UTCGHSA enrichment
- 2026-09-13 19:07 UTCEG score recompute
- 2026-09-13 19:07 UTCVendor advisory
Related CVEs(same product + same vendor + same CWE)
Same vendor
10 shownredhat:RHSA-2026:67491
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
See which npm, PyPI, Go, and Maven packages are affected by 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.