CVE-2026-112052
Received Received - Intake

Integer Overflow in libspatialite Geometry Parsing

Publication date: 2026-10-18

Last updated on: 2026-10-18

Assigner: VulnCheck

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-18
Last Modified
2026-10-18
Generated
2026-10-18
AI Q&A
2026-10-18
EPSS Evaluated
N/A
NVD
CVE-2026-112052
EUVD
EUVD-2026-103514

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
SpatiaLite libspatialite 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-190 The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

libspatialite through version 5.1.0 has an integer overflow flaw in WKB geometry parsing. Attackers can craft a geometry BLOB with a very large point or vertex count. This triggers an overflow in ParseWkbLine and related functions, causing out-of-bounds memory reads on 32-bit systems. This may crash the application or corrupt heap memory.

Detection Guidance

To detect this vulnerability, inspect SpatiaLite databases or applications using libspatialite 5.1.0 or earlier for malformed WKB geometry data. Check for crashes or memory corruption in 32-bit builds during geometry parsing. Use tools like strings or hex editors to examine geometry BLOBs for unusually large point or vertex counts.

Impact Analysis

On 32-bit systems, this flaw could let attackers crash applications using libspatialite or corrupt memory, potentially leading to denial-of-service or unauthorized code execution. Users of SpatiaLite databases or applications parsing WKB geometries are at risk if they use vulnerable versions.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by enabling out-of-bounds memory reads or heap corruption in applications processing spatial data. If exploited, it may lead to unauthorized data access, data integrity issues, or denial-of-service conditions, which are critical risks under these regulations. Systems handling sensitive personal or health data must ensure robust input validation to mitigate such vulnerabilities.

Mitigation Strategies

Upgrade libspatialite to a version beyond 5.1.0. If upgrading is not possible, restrict access to applications processing SpatiaLite databases, especially on 32-bit systems. Monitor for crashes or memory corruption in geometry parsing functions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-112052. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart