Skip to content
major vulnerability· requires attention

Affects IBM Db2, a widely used enterprise database; denial of service against DB servers can disrupt critical business operations and warrants broad IT awareness.

Applications

CVE-2026-87958

8.1
High
EPSS 0.21%Patch availableSep 12, 2026

Privileged-user can disable Db2 server functionality causing denial of service

common questions

Is CVE-2026-87958 being exploited?

Not confirmed. CVE-2026-87958 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.

How severe is CVE-2026-87958?

CVE-2026-87958 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-87958?

Yes. A fix has been recorded for CVE-2026-87958. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-87958 affect?

CVE-2026-87958 affects IBM Db2 11.5.0 - 11.5.9, IBM Db2 12.1.0 - 12.1.5. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-87958?

Apply vendor advisory updates and restrict administrative access immediately

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
IBM Db2 11.5.0 - 11.5.9IBM Db2 12.1.0 - 12.1.5
impact

A privileged/local user can disable Db2 server functionality, causing denial of service and database unavailability.

action required

Patch when possible

affected versions
IBM Db2
  • affected>= 11.5.0 and <= 11.5.9
  • affected>= 12.1.0 and <= 12.1.5

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free