CVE-2026-112048
libspatialite through 5.1.0 Uncontrolled Memory Allocation via ParseWkbPolygon Ring Count
CVSS Score
6.1
EPSS Score
0.0%
EPSS Percentile
0th
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.
| CWE | CWE-789 |
| Vendor | spatialite |
| Product | libspatialite |
| Published | Oct 18, 2026 |
Stay Ahead of the Next One
Get instant alerts for spatialite libspatialite
Be the first to know when new medium vulnerabilities affecting spatialite libspatialite are published — delivered to Slack, Telegram or Discord.
Get Free Alerts →
Free · No credit card · 60 sec setup
CVSS v3 Breakdown
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High
Affected Versions
SpatiaLite / libspatialite
0 ≤ 5.1.0
References
hackmd.io: https://hackmd.io/@haindpwn/libspatialite-wkb-geometry-count-overflow gaia-gis.it: https://www.gaia-gis.it/fossil/libspatialite/file?name=src/gaiageo/gg_wkb.c&ci=5a5528e8d2 vulncheck.com: https://www.vulncheck.com/advisories/libspatialite-through-5.1.0-uncontrolled-memory-allocation-via-parsewkbpolygon-ring-count
Credits
HaiND from the Post and Telecommunication Institute of Technology