Quick answers
- Is CVE-2026-105465 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105465 being exploited in the wild.
- How severe is CVE-2026-105465?
- High severity, with a CVSS score of 8.8, published 12 October 2026.
- Which products and versions are affected?
- IBM Db2 11.5.0 through 11.5.9, 12.1.0 through 12.1.5.
- Is there a fix for CVE-2026-105465?
- Yes: fixed in V11.5: Security Update #94236 or later for V11.5.9; V12.1: Security Update #94722 or later for V12.1.4 and Security Update #94858 or later for V12.1.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105465 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-105465?
- Check whether you run IBM Db2 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: V11.5: Security Update #94236 or later for V11.5.9; V12.1: Security Update #94722 or later for V12.1.4 and Security Update #94858 or later for V12.1.5
Technical details
The vulnerability is an improper privilege management flaw (CWE-269) in the db2locssh component when enabled on the db2 instance. It requires local access with existing user privileges but no user interaction. A successful exploit allows privilege escalation to gain elevated database access. Fixes are available in security updates for affected versions.
Affected products
- IBM Db2 11.5.0 through 11.5.9, 12.1.0 through 12.1.5
Timeline
- 2026-10-08: disclosed