dbcve.org
Db2 High Performance Unload LoadApplication · Ibm

CVE-2025-33131

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-28
Fix available
A fix is available. Upgrade to after 6.1.0.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 allocated on the stack.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Stack-based buffer overflow in IBM DB2 High Performance Unload allows authenticated users to overwrite a buffer allocated on the stack, causing a denial of service via program crash.

MitigationApply IBM fix packs or security updates for the affected versions; as an interim measure, restrict database access to trusted authenticated users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Db2 High Performance Unload LoadApplication
Affected:>= 5.1.0.0, <= 6.1.0.0= 6.1.0.1= 6.1.0.2= 6.1.0.3= 6.5.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm IBM DB2 High Performance Unload is installed
    Locate the DB2 High Performance Unload binary or installation directory. Typical DB2 installations contain this tool under the DB2 installation path, often in a subdirectory related to HPU or tools. Check for executables named 'db2hpu' or similar HPU-specific binaries.
    Affected if The product is present on the system
  2. Determine the installed HPU version
    Run the version command for the High Performance Unload tool. In DB2 environments, this is typically done via 'db2hpu -version' or by querying the HPU component through DB2 commands. You may also check the installation manifest or version file within the HPU installation directory.
    Affected if The version falls within 5.1.0.0 through 6.1.0.0, equals 6.1.0.1, 6.1.0.2, 6.1.0.3, or equals 6.5.0.0
  3. Verify the High Performance Unload feature is accessible
    Confirm that the HPU functionality is available to authenticated database users. This vulnerability requires an authenticated user to invoke the unload operation. Check database permissions and user access to the HPU unload functionality.
    Affected if Authenticated users have access to execute HPU unload operations

The environment is affected if IBM DB2 High Performance Unload is installed with a version in the range 5.1.0.0 to 6.1.0.0, or versions 6.1.0.1, 6.1.0.2, 6.1.0.3, or 6.5.0.0, and authenticated users can access the unload feature.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 6.1.0.0
Interim mitigation

Apply IBM fix packs or security updates for the affected versions; as an interim measure, restrict database access to trusted authenticated users only.

Recommended fix Moderate confidence

IBM DB2 High Performance Unload version 6.5.0.0 IF1 or later (as mentioned in the official description as a fixed release)

  1. 1. Identify the currently installed IBM DB2 High Performance Unload version using the db2pd or ls -la commands.
  2. 2. Confirm the version falls within the affected range: 5.1.0.0 through 6.1.0.3 (including specific versions 6.1.0.1, 6.1.0.2, and 6.1.0.3).
  3. 3. Contact IBM Support or visit the IBM Fix Central website to obtain the latest fixed version for DB2 High Performance Unload.
  4. 4. Download the appropriate patch or upgrade package for your platform (AIX, Linux, Windows, or z/OS).
  5. 5. Schedule a maintenance window and back up all critical databases and configurations.
  6. 6. Stop all DB2 High Performance Unload processes and related services.
  7. 7. Apply the upgrade following IBM's standard installation documentation for your specific platform.
  8. 8. Restart the DB2 High Performance Unload service and verify the version has been updated.
Caveat Standard upgrade risks apply - test in non-production environment first; verify compatibility with your DB2 version and operating system

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Db2 High Performance Unload Load Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33131 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-33131 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data