MobilityDB Files

This is a security release for 1.2. All users of 1.2.0 and 1.2.1 should upgrade.

Security

MobilityDB 1.2.2 fixes CVE-2026-102639 (GHSA-2c92-2w7c-pm3g), an out-of-bounds read in the Well-Known Binary (WKB) input of temporal, set and span values. A crafted binary value, for example a ttext whose text length is negative, passed the bounds check of the WKB reader, so any database user able to call a binary input function (ttextFromBinary, ttextFromHexWKB, the binary receive functions used by COPY ... BINARY and binary protocol parameters) could crash the PostgreSQL backend. In this release every read is compared with the bytes left in the buffer, lengths and counts are checked before they are used, the type code of the header is validated, and parsing stops at the first failed check.

Credit: Harsh Raj Singhania, who reported the issue through VulnCheck.

The 1.1 series receives no fix; its users should upgrade to 1.2.2 or 1.3.1.

Upgrading

Compile and install MobilityDB 1.2.2, then run in each database:

:::sql
ALTER EXTENSION mobilitydb UPDATE TO '1.2.2';

The upgrade changes no SQL definition; the fix is in the library.

What's Changed

• Bound every WKB read by the bytes left in the buffer by @estebanzimanyi in https://github.com/MobilityDB/MobilityDB/pull/2866
• Bump stable-1.2 to 1.2.2 with its upgrade file from 1.2.1 by @estebanzimanyi in https://github.com/MobilityDB/MobilityDB/pull/2870

Full Changelog: https://github.com/MobilityDB/MobilityDB/compare/v1.2.1...v1.2.2