CVE-2026-73515

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 5 sources updated this weekElevated

Also known asEUVD-2026-58108 (ENISA EUVD) · GHSA-qv7r-wgc7-6mc6 (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
46th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 13, 2026

Last Modified

September 24, 2026

Advisory Details (3)

Auto-updated Aug 13, 2026
Patch available.
Web page

PostGIS < 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-buffer
Web page

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/

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpostgresql:18-9080020260914093252.rhel92026-09-16redhat
redhatpostgresql:16-9080020260907191505.rhel92026-09-15redhat
redhatpostgresql18-postgis-0:3.5.3-1.el10_2.12026-09-14redhat
redhatpostgresql16-postgis-0:3.5.3-4.el10_2.12026-09-09redhat

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)
PackageVulnerable rangeFix by version rangeDependents
postgis3.3.2+dfsg-1 ... 3.7.0~rc2+dfsg-1~exp1 (67 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
postgis3.5.2+dfsg-1 ... 3.7.0~rc2+dfsg-1~exp1 (23 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
postgis3.5.2+dfsg-1 ... 3.7.0~rc2+dfsg-1~exp1 (23 versions)
  • every version on: no fix on record
—

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 11× in last 7d / 62× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 282 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 182 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-73515?
CVE-2026-73515 is a high-severity vulnerability; its CVE record was published on August 13, 2026. 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…
When was CVE-2026-73515 made public?
CVE-2026-73515 was made public on August 9, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 13, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-73515 actively exploited?
CVE-2026-73515 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73515?
CVE-2026-73515 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73515?
A fix for CVE-2026-73515 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73515 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73515

Explore →

Is Your Infrastructure Affected by CVE-2026-73515?

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