CVE-2026-1718: 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

Routine

HIGH 7.1UPGRADE

CVE-2026-1718 is a high-severity flaw (CVSS 7.1) 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 with a specially crafted query when autonomous transactions are enabled.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 70%)
CISA exploited list	No
Weakness	CWE-770
Published	2026-05-27
Last modified	2026-10-26

Publisher (CNA): IBM Corporation · Vendor: ibm

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

Am I affected?

Timeline

2026-05-27 14:16 UTCPublished CVE record published
2026-10-26 11: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-1718?

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

Is CVE-2026-1718 being exploited?

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

CVE-2026-1718 affects db2. Severity is high (CVSS 7.1). 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 crafted query when autonomous transactions are enabled.

How urgent is CVE-2026-1718?

Priority 32/100. High severity

Related CVEs

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
CVE-2026-9762 HIGH 7.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 when jdbc url
CVE-2026-7771 MEDIUM 5.5 UPGRADE IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 is vulnerable to a trap when compiling a specially cr

References

← Back to latest CVEs