CVE-2025-33133: IBM DB2 High Performance Unload · Out-of-bounds Write
Affects IBM DB2 High Performance UnloadSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 2025
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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBM DB2 High Performance Unload | Affected
| Fixed in– |
AI-suggested
1. Monitor IBM’s official channels for patches or updates addressing CVE-2025-33133 and apply them promptly once available. 2. Restrict network access to the DB2 High Performance Unload service using firewalls and network segmentation to limit exposure to trusted users and systems only. 3. Enforce strong authentication and access controls to minimize the risk of credential compromise, including multi-factor authentication where possible. 4. Audit and monitor DB2 logs and system behavior for unusual crashes or service disruptions that could indicate exploitation attempts. 5. Implement least privilege principles for users with access to DB2 unload functions to reduce the attack surface. 6. Consider temporary workarounds such as disabling or limiting the use of the High Performance Unload feature if feasible until patches are applied. 7. Conduct regular security awareness training to prevent credential theft and insider threats. 8. Prepare incident response plans to quickly address potential denial of service events impacting DB2 services.
Description
IBM DB2 High Performance Unload 6.1.0.3, 5.1.0.1, 6.1.0.2, 6.5, 6.5.0.0 IF1, 6.1.0.1, 6.1, and 5.1 could allow an authenticated user to cause the program to crash due an out of bounds write.