# CVE-2026-102639: MobilityDB through 1.3.0 Out-of-bounds Read DoS via WKB Deserialization

> Unprivileged users can crash the PostgreSQL backend via crafted WKB payloads due to integer overflow in MobilityDB deserialization.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-2c92-2w7c-pm3g

## What is CVE-2026-102639?

CVE-2026-102639 is a high-severity vulnerability in MobilityDB, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-195 (Signed to Unsigned Conversion Error)

## Which versions are affected by CVE-2026-102639?


## How do I fix CVE-2026-102639?

No fix has been published for CVE-2026-102639 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102639 being exploited?

There is no known exploitation of CVE-2026-102639 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102639 and fix it if it is affected.

What it is: CVE-2026-102639 is a high-severity vulnerability in MobilityDB, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102639 in the wild and no public exploit code.

Affected product: MobilityDB. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102639/ (Markdown: https://insights.sbomify.com/CVE-2026-102639/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102639
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102639
- OSV: https://osv.dev/vulnerability/CVE-2026-102639

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102639/
Summaries are generated and may contain mistakes; the official description above is the record.