CVE-2026-112048CWE-789

CVE-2026-112048

Medium · published October 18, 2026

CVSS v3.1
6.1
EPSS
0%
Percentile
1.6
In the wild
Unconfirmed
What it is

libspatialite through 5.1.0 fails to validate the polygon ring count in ParseWkbPolygon, allowing attackers to trigger uncontrolled interior-ring allocation via crafted geometry BLOBs. Attackers can supply a crafted polygon in a SpatiaLite database or ST_GeomFromWKB input to crash the process or corrupt heap memory on 32-bit builds.

The record
Technical detail
CVSS v3.1
6.1 · MEDIUM
Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
CVSS v4.0
6.9 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
EPSS
0.00118 · 1.6th percentile
Weakness
CWE-789 · Memory Allocation with Excessive Size Value
Published
2026-10-18T17:16Z
References (4)
https://hackmd.io/@haindpwn/libspatialite-wkb-geometry-count-overflow · [email protected]https://www.gaia-gis.it/fossil/libspatialite/file?name=src/gaiageo/gg_wkb.c&ci=5a5528e8d2 · [email protected]https://www.vulncheck.com/advisories/libspatialite-through-5.1.0-uncontrolled-memory-allocation-via-parsewkbpolygon-ring-count · [email protected]https://hackmd.io/@haindpwn/libspatialite-wkb-geometry-count-overflow · 134c704f-9b21-4f2e-91b3-4a467353bcc0
EPSS history
Timeline
  • 20 OCT 03:29Z
    EPSS moved — → 0%
    epss
  • 18 OCT 12:19Z
    libspatialite through 5.1.0 Uncontrolled Memory Allocation via ParseWkbPolygon Ring Count
    cvelistv5
  • 18 OCT 12:19Z
    libspatialite through 5.1.0 Uncontrolled Memory Allocation via ParseWkbPolygon Ring Count
    cvelistv5