CVE-2025-33126
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 · uneditedIBM 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, 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, and 5.1 could allow an authenticated user to cause the program to crash due to the incorrect calculation of a buffer size.
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 confidenceIBM DB2 High Performance Unload contains a buffer size calculation error that allows an authenticated attacker to cause the program to crash (Denial of Service). The vulnerability is exploitable over the network with low complexity and requires only low privileges.
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>= 5.1.0.0, <= 6.1.0.0= 6.1.0.1= 6.1.0.2= 6.1.0.3= 6.5.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify IBM DB2 High Performance Unload is installedLocate the db2hpu binary or check for DB2 High Performance Unload installation directories (typically under /opt/ibm/db2hpu or $DB2DIR/hpu). Use command: which db2hpu or ls -la /opt/ibm/ | grep -i db2Affected if The product is not installed on the system
-
Determine the installed versionRun the version command for db2hpu, typically: db2hpu -version or check the installation manifest. On Linux/Unix: cat /opt/ibm/db2hpu/version.properties 2>/dev/nullAffected if The installed version falls within >= 5.1.0.0 and <= 6.1.0.0, OR equals 6.1.0.1, 6.1.0.2, 6.1.0.3, or 6.5.0.0
-
Verify network exposureCheck if the DB2 High Performance Unload service is listening on network ports. Review db2hpu configuration files (db2hpu.conf) for network binding settings. Use: netstat -anp | grep -i db2hpu or check listening ports in /etc/servicesAffected if The service is exposed to untrusted network interfaces
-
Check authentication configurationReview the DB2 High Performance Unload authentication settings in its configuration file. Look for allowlist/denylist settings or user access controls. Check if guest or anonymous access is enabledAffected if Low-privileged or unauthenticated network access is permitted
The environment is affected if IBM DB2 High Performance Unload is installed with a version matching 5.1.0.0 through 6.1.0.0, 6.1.0.1-6.1.0.3, or 6.5.0.0 AND the service is network-accessible to untrusted users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply IBM-supplied patches for the affected versions or upgrade to a patched release. As a compensating control, restrict network access to trusted authenticated users only.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-33126 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-33126 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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