# CVE-2026-102469: Deserialization in Eclipse Vert.x

> A malicious DRDA server can trigger unsafe Java deserialization in the Vert.x DB2 client, potentially leading to remote code execution or denial of service.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-j4vf-w939-pgxf, GHSA-mxgf-c753-mmc9

## What is CVE-2026-102469?

CVE-2026-102469 is a critical unsafe deserialization vulnerability in Eclipse Vert.x, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Eclipse Vert.x versions [4.0.0, 4.5.34] or [5.0.0,5.0.12] or [5.1.0,5.1.9] or [5.2.0, 5.2.0], the Vert.x DB2 client (vertx-db2-client) contains DRDA protocol handling code that deserializes User Defined Type (UDT) column data using a bare ObjectInputStream.readObject() call with no ObjectInputFilter or class allowlist.

This code path is triggered when a DRDA server sends a result set with a column tagged as UDT (FDOCA protocol LID 0x50). However, DB2 does not support this type of UDT. The FDOCA 0x50 type is never sent by a legitimate DB2 server.

Nevertheless, a malicious or man-in-the-middle DRDA server could craft a response with a 0x50-tagged column, causing the client to deserialize arbitrary attacker-controlled bytes on the Vert.x event loop before any application code can inspect or reject the data. If a Java deserialization gadget chain is present on the application's classpath, this enables remote code execution. Without a gadget chain, denial of service is possible via crafted object graphs. TLS is disabled by default, making man-in-the-middle exploitation feasible.

The impacted component is io.vertx:vertx-db2-client.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Eclipse Vert.x.

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

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

## Is CVE-2026-102469 being exploited?

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

## Other vulnerabilities in Eclipse Vert.x

- [CVE-2019-17640](https://insights.sbomify.com/CVE-2019-17640/): Path Traversal in Eclipse Vert (critical 9.8)
- [CVE-2018-12542](https://insights.sbomify.com/CVE-2018-12542/): Eclipse Vert.x does not properly neutralize '' (forward slashes) sequences that can resolve to an external location (critical 9.8)
- [CVE-2018-12544](https://insights.sbomify.com/CVE-2018-12544/): Moderate severity vulnerability that affects io.vertx:vertx-core (critical 9.8)
- [CVE-2018-12540](https://insights.sbomify.com/CVE-2018-12540/): High severity vulnerability that affects io.vertx:vertx-web (high 8.8)
- [CVE-2026-102461](https://insights.sbomify.com/CVE-2026-102461/): Denial of service in Eclipse Vert.x (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102469 is a critical unsafe deserialization vulnerability in Eclipse Vert.x, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102469 in the wild and no public exploit code.

Affected product: Eclipse Vert.x. 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-102469/ (Markdown: https://insights.sbomify.com/CVE-2026-102469/index.md)
```

## Sources

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

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