libspatialite up to 5.1.0 WKB Parser gg_wkb.c ParseWkbLine integer overflow

Summaryinfo

A vulnerability has been found in libspatialite up to 5.1.0 and classified as critical. Affected is the function ParseWkbLine of the file gg_wkb.c of the component WKB Parser. The manipulation leads to integer overflow. This vulnerability is traded as CVE-2026-112052. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in libspatialite up to 5.1.0. It has been rated as critical. This issue affects the function ParseWkbLine of the file gg_wkb.c of the component WKB Parser. The manipulation with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to 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 can introduce other weaknesses when the calculation is used for resource management or execution control. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at hackmd.io. The identification of this vulnerability is CVE-2026-112052 since 10/18/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/18/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• libspatialite

Version

• 5.0
• 5.1.0

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion