Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-10109: 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 imprope

57
This month
CRITICAL 9.8REMOTEUPGRADE

CVE-2026-10109 is a critical-severity flaw (CVSS 9.8) affecting db2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Critical severity
  • CISA SSVC: automatable with total technical impact
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.9% (top 42%)
CISA exploited listNo
WeaknessCWE-94
Published2026-06-30
Last modified2026-10-25
Publisher (CNA): IBM Corporation · Vendor: ibm

Share: LinkedIn · X · Reddit

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

ibm db2 UPGRADE
Affected: >= 11.5.0 and <= 11.5.9 · >= 12.1.0 and <= 12.1.4
Fixed in: newer than 12.1.4
Safe to downgrade to: a release before 11.5.0
1. Check installed version
apt-cache policy db2 || rpm -q db2 || db2 --version
2. UPGRADE to newer than 12.1.4 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade db2
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade db2
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 11.5.0 (Debian / Ubuntu)
apt-cache madison db2 sudo apt install db2=<VERSION_BEFORE_11.5.0> sudo apt-mark hold db2
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list db2 sudo dnf downgrade db2-<VERSION_BEFORE_11.5.0> sudo dnf versionlock add db2
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Fedora 46 · mingw-qt5-qtwebkit · FIXED · 5.212.0-0.46.alpha4.fc46 · FEDORA-2026-46ae541c22 · source
sudo dnf upgrade --advisory=FEDORA-2026-46ae541c22
Fedora ELN · kdominate · FIXED · 26.08.2-2.eln159 · FEDORA-2026-b1d98239fd · source
sudo dnf upgrade --advisory=FEDORA-2026-b1d98239fd
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-10109?

db2: upgrade to newer than 12.1.4. Exact commands for each OS are on this page.

Is CVE-2026-10109 being exploited?

CVE-2026-10109 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-10109 affect?

CVE-2026-10109 affects db2. Severity is critical (CVSS 9.8). 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.

How urgent is CVE-2026-10109?

Priority 57/100. Critical severity; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.