MobilityDB up to 1.1.2/1.2.1/1.3.0 WKB Deserialization wkb_parse_state_check out-of-bounds

Summaryinfo

A vulnerability, which was classified as critical, has been found in MobilityDB up to 1.1.2/1.2.1/1.3.0. This issue affects the function wkb_parse_state_check of the component WKB Deserialization. Performing a manipulation results in out-of-bounds. This vulnerability is reported as CVE-2026-102639. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in MobilityDB up to 1.1.2/1.2.1/1.3.0. It has been classified as critical. This affects the function wkb_parse_state_check of the component WKB Deserialization. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on availability. The summary by CVE is:

MobilityDB version 1.3.0 and earlier contains an out-of-bounds read vulnerability in the MEOS binary and library WKB deserialization logic that allows unprivileged database users to crash the PostgreSQL backend process by supplying a crafted WKB payload with a negative length field. The negative length value wraps to a large unsigned size_t due to missing signed validation, bypasses an overflow-unsafe pointer arithmetic bounds check in wkb_parse_state_check(), and causes memcpy() in text_from_wkb_state() to operate with a corrupted unbounded length, resulting in a remote denial-of-service condition affecting all sessions on the PostgreSQL instance.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-102639 since 09/29/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available.

Upgrading to version 1.2.2 or 1.3.1 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• MobilityDB

Version

• 1.0
• 1.1
• 1.1.0
• 1.1.1
• 1.1.2
• 1.2
• 1.2.0
• 1.2.1
• 1.3.0

Website

• Product: https://github.com/MobilityDB/MobilityDB/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion