CVE-2026-6053: IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 is vulnerable to a denial of service when a specially

Routine

MEDIUM 5.5UPGRADE

CVE-2026-6053 is a medium-severity flaw (CVSS 5.5) 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 a denial of service when a specially crafted query is run with range partitioned tables.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.1% (top 99%)
CISA exploited list	No
Weakness	CWE-770
Published	2026-05-27
Last modified	2026-10-14

Publisher (CNA): IBM Corporation · Vendor: ibm

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

Am I affected?

Timeline

2026-05-27 14:17 UTCPublished CVE record published
2026-10-14 20:10 UTCUpdated Record last modified

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.

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-6053?

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

Is CVE-2026-6053 being exploited?

CVE-2026-6053 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-6053 affect?

CVE-2026-6053 affects db2. Severity is medium (CVSS 5.5). IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 is vulnerable to a denial of service when a specially crafted query is run with range partitioned tables.

How urgent is CVE-2026-6053?

Priority 19/100. No elevated risk signals yet.

Related CVEs

CVE-2026-1577 MEDIUM 6.5 UPGRADE UPGRADE IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 for Linux, UNIX and Windows (includes Db2 Connect Ser
CVE-2026-1718 HIGH 7.1 UPGRADE IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 is vulnerable to a denial of service with a specially
CVE-2026-1352 MEDIUM 6.5 UPGRADE UPGRADE IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 for Linux, UNIX and Windows (includes Db2 Connect Ser
CVE-2026-10109 CRITICAL 9.8 UPGRADE 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
CVE-2026-11906 MEDIUM 6.5 UPGRADE IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 for Linux, UNIX and Windows (includes Db2 Connect Ser

References

← Back to latest CVEs