AIKIDO-2026-240494
vertx-db2-client is vulnerable to Insecure Deserialization
81
CVE Score
High
Insecure Deserialization
TL;DR
vertx-db2-client deserializes a column tagged as a user-defined type with ObjectInputStream.readObject and no class filter. A DRDA server that sends FDOCA type 0x50 can supply that stream before application code sees the row. A legitimate DB2 server does not send this type. The fix removes that deserialization path.
How do I fix this?
Upgrade the io.vertx:vertx-db2-client library to the patch version.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and the client connects to a DRDA server you do not trust.
Package
Versions
4.0.0 - 4.5.34
Fixed in 4.5.355.0.0 - 5.1.8
Fixed in 5.1.105.2.0 - 5.2.0
Fixed in 5.2.1Background info
vertx-db2-client is vulnerable to Insecure Deserialization in versions 4.0.0 - 4.5.34, 5.0.0 - 5.1.8 and 5.2.0 - 5.2.0.
Links
Get secure today,
quickly and for free.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPAuthorized© All Intel data is openly available and commercially licensed.