Live › vulnerability › CVE-2026-112052
Go to dashboardlibspatialite through 5.1.0 has an integer overflow in the point and vertex count size check used when parsing WKB geometry in gg_wkb.c. A crafted geometry BLOB with a large point count can crash the process or corrupt heap memory on 32-bit builds.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications that load SpatiaLite databases or parse WKB geometry blobs from files or users with libspatialite 5.1.0 or earlier. The risk is highest on 32-bit builds, where the overflow corrupts memory; systems that only use trusted, locally created spatial data are less exposed.
No product ranges from the sources yet.
spatialite --version or check the libspatialite version in the application's dependencies, and compare against 5.1.0libspatialite in a Debian or Alpine package list)5.1.0 once a patched release is available; unknown whether one has shippedEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
libspatialite through 5.1.0 contains an integer overflow vulnerability in the WKB point and vertex count size guard of ParseWkbLine and related parsers in gg_wkb.c, allowing out-of-bounds reads. Attackers can supply a crafted geometry BLOB with a large point count, for example in a SpatiaLite database file, to crash the process or corrupt heap memory on 32-bit builds.
This page as .md · .json · in your agent: get_signal("CVE-2026-112052")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.