CVE-2026-10109
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM Db2 versions 11.5.0-11.5.9 and 12.1.0-12.1.4 contain a critical remote code execution vulnerability in the DRDA (Distributed Relational Database Architecture) protocol handshake that occurs before authentication. An unauthenticated attacker can exploit improper handling of the pre-authentication DRDA handshake to execute arbitrary code on the affected system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 11.5.0, <= 11.5.9>= 12.1.0, <= 12.1.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Db2 versionRun 'db2level' command from a Db2 instance user, or query the DB2_GET_VERSION_INFO administrative view using: 'SELECT * FROM SYSIBMADM.DB2_GET_VERSION_INFO'Affected if The returned version falls within 11.5.0-11.5.9 or 12.1.0-12.1.4
-
Verify DRDA listener is activeCheck if Db2 is listening on the DRDA port (default 50000/tcp). Use 'netstat -an | grep 50000' or 'ss -tlnp | grep 50000' to confirm the port is in LISTEN stateAffected if Port 50000/tcp (or configured Db2 port) is open and listening
-
Assess network exposure of Db2 listenerReview firewall rules, network ACLs, or cloud security groups to determine if the DRDA port is accessible from untrusted networks. Check if the listener is bound to 0.0.0.0 or an externally accessible IPAffected if The DRDA port is reachable from networks that contain untrusted or internet-facing hosts without additional access controls
-
Confirm remote access is enabledCheck Db2 configuration for remote connections: run 'db2 get dbm cfg | grep -i svcename' to identify the service name, then verify service configuration allows TCP/IP connectionsAffected if Remote TCP/IP connections are enabled and the service is configured for network listening
The environment is affected if Db2 version is 11.5.0-11.5.9 or 12.1.0-12.1.4 AND the DRDA listener port is network-accessible to untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply IBM's security patches for the specific Db2 version or upgrade to a patched version. If immediate patching is not possible, consider network segmentation to restrict untrusted access to the Db2 port (50000/tcp typically).
Db2 11.5.10+ or 12.1.5+ (latest available fix pack)
- Verify current Db2 version by running: db2level (Linux/Unix) or db2start (Windows)
- Download IBM Db2 fix pack from IBM Fix Central (https://www.ibm.com/support/fixcentral/)
- For Db2 11.5.x: Upgrade to version 11.5.10 or later
- For Db2 12.1.x: Upgrade to version 12.1.5 or later
- Apply the upgrade following IBM's standard Db2 fix pack installation procedures
- Restart Db2 instance after upgrade: db2stop force && db2start
- Verify the new version is running: db2level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10109 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10109 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data