PatchSiren cyber security CVE debrief
CVE-2026-105464 IBM CVE debrief
IBM Db2 vulnerability CVE-2026-105464 allows local attackers with DBADM authorization to gain elevated privileges due to improper privilege management. Affected versions include 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 for Linux, UNIX, and Windows. This vulnerability has a high severity and requires immediate attention from Db2 administrators and security teams to assess exposure and apply patches. The vulnerability allows local attackers to gain elevated privileges, which can lead to unauthorized access and control of sensitive data.
- Vendor
- IBM
- Product
- Db2
- CVSS
- HIGH 8.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-12
- Original CVE updated
- 2026-10-13
- Advisory published
- 2026-10-12
- Advisory updated
- 2026-10-13
Who should care
Db2 administrators, security teams, and IT personnel responsible for Linux, UNIX, and Windows systems should assess exposure, verify and apply patches, and monitor for suspicious activity with DBADM authorization. These stakeholders should review and update access controls for Db2 to prevent local privilege escalation.
Why it matters
CVE-2026-105464 is a high-severity vulnerability in IBM Db2 that allows local attackers with DBADM authorization to gain elevated privileges. Db2 administrators and security teams should assess exposure, verify and apply patches, and monitor for suspicious activity.
- Verify and apply patches to prevent local privilege escalation
- Assess exposure of Db2 installations to CVE-2026-105464
- Monitor for suspicious local activity with DBADM authorization
- Review and update access controls for Db2
Technical summary
CVE-2026-105464 is a high-severity vulnerability in IBM Db2 that allows local attackers with DBADM authorization to gain elevated privileges due to improper privilege management. The vulnerability affects Db2 versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 for Linux, UNIX, and Windows.
Defensive priority
High priority for Db2 administrators to assess exposure and apply patches
Recommended defensive actions
- Assess exposure of Db2 installations to CVE-2026-105464
- Verify and apply IBM patches for affected versions
- Monitor for local attacks with DBADM authorization
- Review and update access controls for Db2
Evidence notes
The CVE record and source item provide details on the vulnerability and affected versions. IBM has released a vendor advisory with patch information. The vulnerability affects Db2 versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 for Linux, UNIX, and Windows. Defenders should verify and apply patches to prevent local privilege escalation and monitor for suspicious activity with DBADM authorization. The source item provides additional details on the vulnerability, but the scope,
Sources and references
Verified primary and authoritative sources
-
CVE-2026-105464 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-105464
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-105464 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-105464
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
IBM® Db2® is vulnerable to a local attacker with DBADM authorization gaining elevated privileges
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/105xxx/CVE-2026-105464.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://www.ibm.com/support/pages/node/7291613
Supplemental source - vendor-advisory, patch
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.