CVE-2026-86087: IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an authenticated user to send a specially

Routine

MEDIUM 4.3UPGRADE

CVE-2026-86087 is a medium-severity flaw (CVSS 4.3) 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.5 could allow an authenticated user to send a specially crafted request to write arbitrary files on the system.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 73%)
CISA exploited list	No
Weakness	CWE-22
Published	2026-09-10
Last modified	2026-09-14

Publisher (CNA): IBM Corporation · Vendor: ibm

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

Am I affected?

Timeline

2026-09-10 22:17 UTCPublished CVE record published
2026-09-14 20:10 UTCUpdated Record last modified

ibm db2 UPGRADE

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

Fixed in: newer than 12.1.5

Safe to downgrade to: a release before 11.5

1. Check installed version

apt-cache policy db2 || rpm -q db2 || db2 --version

2. UPGRADE to newer than 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 (Debian / Ubuntu)

apt-cache madison db2 sudo apt install db2=<VERSION_BEFORE_11.5> 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> 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-86087?

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

Is CVE-2026-86087 being exploited?

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

CVE-2026-86087 affects db2. Severity is medium (CVSS 4.3). IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an authenticated user to send a specially crafted request to write arbitrary files on the system.

How urgent is CVE-2026-86087?

Priority 22/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