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

Routine

MEDIUM 5.5UPGRADE

CVE-2026-7771 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 trap when compiling a specially crafted statements containing subqueries could lead to a denial of service.

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	None
User interaction	Required
EPSS exploit chance	0.1% (top 96%)
CISA exploited list	No
Weakness	CWE-835
Published	2026-07-17
Last modified	2026-10-24

Publisher (CNA): IBM Corporation · Vendor: ibm

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

Am I affected?

Timeline

2026-07-17 20:17 UTCPublished CVE record published
2026-10-24 20:10 UTCUpdated Record last modified

ibm db2 UPGRADE

Affected: >= 11.5.0 and <= 11.5.9 · >= 12.1.0 and < 12.1.5

Fixed in: 12.1.5

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 12.1.5 (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-7771?

db2: upgrade to 12.1.5. Exact commands for each OS are on this page.

Is CVE-2026-7771 being exploited?

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

CVE-2026-7771 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 trap when compiling a specially crafted statements containing subqueries could lead to a denial of service.

How urgent is CVE-2026-7771?

Priority 20/100. No elevated risk signals yet.

Related CVEs

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-10535 HIGH 8.4 UPGRADE IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 is vulnerable to buffer overflow in setgid helper db2
CVE-2026-10695 MEDIUM 6.2 UPGRADE IBM Db2 12.1.0 through 12.1.4 federated server is vulnerable to a denial of service when running non fenced fe
CVE-2026-10543 HIGH 8.2 UPGRADE IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to privilege escalation with a speciall
CVE-2026-10534 HIGH 8.4 UPGRADE IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to buffer overflow in the IXF IMPORT pa

References

← Back to latest CVEs