Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Pre-auth DRDA handshake is network-reachable with no credentials or interaction (AV:N/AC:L/PR:N/UI:N), and code injection yields full host compromise (C/I/A:H).
Primary rating from Vendor (us).
CVSS VectorVendor: us
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
2DescriptionCVE.org
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 is vulnerable to remote code execution due to improper pre-auth DRDA handshake handling.
AnalysisAI
Remote code execution in IBM Db2 11.5.0-11.5.9 and 12.1.0-12.1.4 lets unauthenticated network attackers run arbitrary code by abusing improper handling of the pre-authentication DRDA handshake. Because the flaw is reachable before any login, any client able to reach the database listener can trigger it, and the CVSS 3.1 base score of 9.8 reflects full compromise of confidentiality, integrity, and availability. No public exploit is identified at time of analysis and the CVE is not listed in CISA KEV.
Technical ContextAI
DRDA (Distributed Relational Database Architecture) is the wire protocol IBM Db2 uses for client-server and inter-server communication, typically exposed on TCP 50000/50001. The vulnerability lies in the server's parsing of the DRDA connection handshake that occurs before authentication completes, meaning the vulnerable code path is exercised by any peer that can open a socket to the listener. The CWE-94 (Improper Control of Generation of Code / code injection) classification indicates the malformed handshake data is ultimately interpreted as executable code or control flow rather than inert input, allowing the attacker to direct execution. Affected distributions span the Db2 11.5 modification stream (11.5.0 through 11.5.9) and the newer 12.1 stream (12.1.0 through 12.1.4); no CPE strings were supplied in the input, so exact platform/edition scoping should be confirmed against IBM's advisory.
RemediationAI
Apply the fixed Db2 level published in IBM's bulletin at https://www.ibm.com/support/pages/node/7277424 as the primary remediation; the input data does not state an exact patched fixpack version, so treat the specific target level as patch available per vendor advisory and confirm it from that page before scheduling the upgrade. As compensating controls until patching, restrict network access to the Db2 listener ports (default TCP 50000/50001) using host and network firewalls so only trusted application hosts can reach the DRDA endpoint, which directly limits pre-auth reachability but will break any client whose source IP is not allowlisted. Where feasible, place Db2 behind a bastion or private subnet and require VPN for administrative access, accepting the added connection latency and operational overhead. Enable and monitor connection logging on the listener to detect anomalous or malformed handshake attempts; this is detective rather than preventive and does not stop exploitation. Do not expose Db2 directly to the internet under any circumstances.
Stack-based buffer overflow in the SQL/PSM (aka SQL Persistent Stored Module) Stored Procedure (SP) infrastructure in IB
IBM DB2 for Linux, UNIX and Windows 9.2, 10.1, 10.5, and 11.1 (includes DB2 Connect Server) is vulnerable to a stack-bas
Stack-based buffer overflow in IBM DB2 9.7 through FP9a, 9.8 through FP5, 10.1 through FP4, and 10.5 before FP4 on Linux
IBM DB2 9.5 uses world-writable permissions for nodes.reg, which has unspecified impact and attack vectors. Rated critic
Privilege escalation in IBM Db2 (data server versions 11.5.0-11.5.9 and 12.1.0-12.1.5) allows an attacker to submit a sp
Memory-corruption in IBM Db2's IXF file IMPORT parser lets an attacker supply a crafted IXF data file that overflows a s
Stack-based buffer overflow in the Java Stored Procedure infrastructure in IBM DB2 9.1 before FP12, 9.5 through FP9, 9.7
Directory traversal vulnerability in the UTL_FILE module in IBM DB2 and DB2 Connect 10.1 before FP1 on Windows allows re
IBM GSKit (IBM DB2 for Linux, UNIX and Windows 9.7, 10.1, 10.5, and 11.1) duplicates the PRNG state across fork() system
Integer signedness error in the db2dasrrm process in the DB2 Administration Server (DAS) in IBM DB2 9.1 through FP11, 9.
The Stored Procedure infrastructure in IBM DB2 9.5, 9.7 before FP9a, 10.1 before FP3a, and 10.5 before FP3a on Windows a
The scalar-function implementation in IBM DB2 9.7 through FP10, 9.8 through FP5, 10.1 before FP5, and 10.5 through FP5 o
Same weakness CWE-94 – Code Injection
View allSame technique Code Injection
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-40406
GHSA-fq2g-wj3x-6hc2