Db2 High Performance Unload Load vulnerabilitiesRanked by how likely they are to be used.

Product9 versions
The short answer

Db2 High Performance Unload Load is made by IBM. We track 8 published vulnerabilities in it, across 9 versions. None of them is on the list of flaws known to be exploited today. If you run Db2 High Performance Unload Load, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Db2 High Performance Unload Load vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Db2 High Performance Unload Load's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Db2 High Performance Unload Load flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 0.4%

    IBM DB2 High Performance Unload load for LUW 6.1, 6.1.0.1, 6.1.0.1 IF1, 6.1.0.2, 6.1.0.2 IF1, and 6.1.0.1 IF2 db2hpum_debug is a setuid root binary which trusts the PATH environment variable.

    CVSS7.8Published26 Aug 2019
  2. 0.4%

    IBM DB2 High Performance Unload load for LUW 6.1 and 6.5 is vulnerable to a buffer overflow, caused by improper bounds checking which could allow a local attacker to execute arbitrary code on the system with root...

    CVSS7.8Published22 Oct 2019
  3. 0.4%

    IBM DB2 High Performance Unload load for LUW 6.1 and 6.5 could allow a local attacker to execute arbitrary code on the system, caused by an untrusted search path vulnerability.

    CVSS7.8Published12 Dec 2019
  4. 0.3%

    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.

    CVSS6.5Published28 Oct 2025
  5. 0.3%

    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, 5.1, 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, 5.1, 6.1.0.3, 5.1.0.1, 6.1.0.2, 6.5, 6.5.0.0 IF1, 6.1.0.1,...

    CVSS6.5Published28 Oct 2025
  6. 0.3%

    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 a buffer being overwritten when it is...

    CVSS6.5Published28 Oct 2025
  7. 0.3%

    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...

    CVSS6.5Published28 Oct 2025
Precursor Intelligence

Running Db2 High Performance Unload Load? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 8 published vulnerabilities listed under the name Db2 High Performance Unload Load, across 9 versions.

None of Db2 High Performance Unload Load's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Db2 High Performance Unload Load. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.