Skip to main content
VulnerabilityPublished

CVE-2025-33132: IBM DB2 High Performance Unload · Use of sizeof() on a Pointer Type

Affects IBM DB2 High Performance UnloadSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBM DB2 High Performance UnloadAffected
  • 5.1 – 6.5.0.0
8 affected builds
Fixed in–

AI-suggested

European organizations should implement the following specific mitigations: 1) Restrict access to the IBM DB2 High Performance Unload functionality strictly to trusted and necessary users by enforcing the principle of least privilege. 2) Monitor DB2 logs and system behavior for abnormal crashes or unload failures that could indicate exploitation attempts. 3) Employ network segmentation and firewall rules to limit access to DB2 servers from untrusted networks. 4) Prepare incident response plans for potential denial of service events affecting database availability. 5) Engage with IBM support channels to obtain patches or workarounds as soon as they become available and prioritize timely deployment. 6) Consider temporary disabling or restricting use of the High Performance Unload feature if feasible until a patch is applied. 7) Conduct regular security audits and vulnerability assessments focusing on database utilities and privileged user activities.

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 to the incorrect calculation of the size of the data that is being pointed to.

References

Community reviews

Loading reviews…