CVE-2023-38003: IBM Db2 for Linux, UNIX and Windows · 264 Permissions, Privileges, Access Controls
Affects IBM Db2 for Linux, UNIX and WindowsSource CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Dec 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ibmibm/db2pkg:rpm/ibm/db2Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should implement the following specific mitigation measures: 1) Immediately review and audit all accounts with DATAACCESS privileges to ensure that only necessary users have this level of access. Remove or restrict privileges where not absolutely required. 2) Apply the principle of least privilege rigorously within Db2 environments, limiting DATAACCESS privileges to trusted administrators only. 3) Monitor database activity logs for unusual or unauthorized routine executions, focusing on accounts with elevated privileges. 4) Implement enhanced internal controls and segregation of duties to reduce the risk of insider misuse. 5) Stay updated with IBM security advisories and apply patches or fixes as soon as they become available. 6) Consider deploying database activity monitoring (DAM) tools that can detect and alert on suspicious privilege escalations or unauthorized routine executions. 7) Harden network access to Db2 servers by restricting access to trusted hosts and using network segmentation to limit exposure. 8) Conduct regular security training for database administrators and privileged users to raise awareness about the risks associated with excessive privileges. These steps go beyond generic advice by focusing on privilege management, monitoring, and internal controls specific to the Db2 environment and this vulnerability.
Description
IBM Db2 for Linux, UNIX and Windows (includes Db2 Connect Server) 10.5, 11.1, and 11.5 could allow a user with DATAACCESS privileges to execute routines that they should not have access to. IBM X-Force ID: 260214.