---
id: "CVE-2026-112052"
kind: "vulnerability"
aliases: ["CVE-2026-112052"]
title: "libspatialite: integer overflow in WKB parser allows out-of-bounds reads"
severity: "medium"
cvss: 6.9
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["32-bit", "c", "gis", "libspatialite", "package", "spatialite"]
not_affected_if: ["64-bit-build", "trusted-data-only"]
published_at: "2026-10-18T13:16:37+00:00"
first_seen_at: "2026-10-23T21:57:15+00:00"
updated_at: "2026-10-25T03:40:58+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112052", "first_seen_at": "2026-10-23T21:57:15+00:00"}]
---

# libspatialite: integer overflow in WKB parser allows out-of-bounds reads

libspatialite 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, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `spatialite --version` or check the libspatialite version in the application's dependencies, and compare against `5.1.0`
- Look for libspatialite in the build or lockfile (for example `libspatialite` in a Debian or Alpine package list)
- unknown whether a specific fixed version exists in the sources

## Fix

- Upgrade libspatialite past `5.1.0` once a patched release is available; unknown whether one has shipped
- Until then, only open geometry data from trusted sources in SpatiaLite databases

## Timeline

- 2026-10-23T21:57:15+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-112052

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_