CVE-2026-102469
Received Received - Intake

Remote Code Execution in Eclipse Vert.x DB2 Client

Vulnerability report for CVE-2026-102469, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-15

Last updated on: 2026-10-15

Assigner: Eclipse Foundation

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-15
Last Modified
2026-10-15
Generated
2026-10-15
AI Q&A
2026-10-15
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
Eclipse Foundation Eclipse Vert.x 4.0.0
Eclipse Foundation Eclipse Vert.x 5.0.0
Eclipse Foundation Eclipse Vert.x 5.1.0
Eclipse Foundation Eclipse Vert.x 5.2.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an unsafe Java deserialization flaw in the Eclipse Vert.x DB2 client (vertx-db2-client). It occurs when the client deserializes User Defined Type (UDT) column data using ObjectInputStream.readObject() without any security checks. A malicious or man-in-the-middle DRDA server could exploit this by sending a crafted response with a UDT-tagged column (FDOCA protocol LID 0x50), which legitimate DB2 servers never use. This causes the client to deserialize arbitrary attacker-controlled data on the Vert.x event loop before validation.

Detection Guidance

Check if your system uses vulnerable versions of Eclipse Vert.x DB2 client (4.0.0 to 4.5.34, 5.0.0 to 5.0.12, 5.1.0 to 5.1.9, or 5.2.0). Inspect dependencies in your project files (e.g., pom.xml for Maven or build.gradle for Gradle) for io.vertx:vertx-db2-client. Monitor network traffic for DRDA protocol interactions with UDT-tagged columns (FDOCA LID 0x50).

Commands: For Maven, run 'mvn dependency:tree | grep vertx-db2-client'. For Gradle, use 'gradle dependencies | grep vertx-db2-client'. Check logs for deserialization errors or unexpected event loop activity.

Impact Analysis

If a Java deserialization gadget chain is present on the application's classpath, this vulnerability enables remote code execution (RCE). Without a gadget chain, it can still cause denial of service (DoS) via crafted object graphs. The lack of TLS by default makes man-in-the-middle attacks feasible, increasing the risk of exploitation.

Compliance Impact

This vulnerability can lead to unauthorized remote code execution or denial of service, which may result in data breaches or loss of sensitive information. Such incidents could violate GDPR's data protection requirements or HIPAA's security and privacy rules, potentially leading to legal penalties and reputational damage.

Mitigation Strategies

Upgrade to patched versions: 5.2.1, 5.1.10, or 4.5.35. Disable TLS only if absolutely necessary; enable it to prevent man-in-the-middle attacks. Review classpath for Java deserialization gadget chains and remove unused libraries.

Apply network-level mitigations: restrict DRDA server connections, use firewalls to limit exposure, and monitor for suspicious DRDA traffic with UDT-tagged columns.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-102469. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart