CVE-2026-112048
Received Received - Intake

Spatialite Geometry Parsing Heap Overflow via Invalid Polygon Ring Count

Publication date: 2026-10-18

Last updated on: 2026-10-18

Assigner: VulnCheck

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

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-112048
EUVD
EUVD-2026-103510

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-789 The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in libspatialite through version 5.1.0 involves uncontrolled memory allocation in the ParseWkbPolygon function due to insufficient validation of polygon ring counts. Attackers can craft geometry BLOBs with excessive interior-ring allocations, causing process crashes or heap memory corruption, especially on 32-bit systems.

Detection Guidance

To detect this vulnerability, inspect systems using libspatialite versions 5.1.0 or earlier. Check for crashes or memory corruption when processing geometry data. Use tools like gdb to analyze crashes in applications linked to libspatialite. Monitor logs for segmentation faults or heap corruption errors during spatial data processing.

Impact Analysis

This flaw allows attackers to crash applications or corrupt memory by providing maliciously crafted geometry data. It can lead to denial of service or potential arbitrary code execution if exploited through SpatiaLite databases or ST_GeomFromWKB inputs.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR or HIPAA as it is a memory corruption issue in a spatial database library. However, if exploited, it could lead to denial of service or arbitrary code execution, potentially causing data breaches or loss of availability. Such incidents may impact compliance by violating data integrity or availability requirements under these regulations.

Mitigation Strategies

Immediately upgrade libspatialite to a patched version beyond 5.1.0. If upgrading is not possible, restrict user input to trusted sources and disable spatial functions in applications. Apply input validation for geometry BLOBs to prevent crafted inputs. Monitor for unusual memory usage or crashes in spatial processing applications.

Chat Assistant

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

EPSS Chart