Cyber Resilience

CVE-2025-33126

Ibm Db2 High Performance Unload Load 5.1.0.0 – 6.1.0.0

Published
28 October 2025
Modified
05 November 2025
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0029 21th percentile
Risk Priority 49 floored blend · peak EPSS

Summary

CVE-2025-33126 is a medium-severity Incorrect Calculation of Buffer Size (CWE-131) vulnerability in Ibm Db2 High Performance Unload Load. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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, 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,…

more

and 5.1 could allow an authenticated user to cause the program to crash due to the incorrect calculation of a buffer size.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-33132Same product: Ibm Aix
CVE-2025-33131Same product: Ibm Aix
CVE-2025-33133Same product: Ibm Aix
CVE-2023-50308Same product: Ibm Aix
CVE-2023-47141Same product: Ibm Aix
CVE-2023-45193Same product: Ibm Aix
CVE-2026-8835Same product: Ibm Aix
CVE-2026-8834Same product: Ibm Aix
CVE-2026-8854Same product: Ibm Aix
CVE-2023-35012Same product: Ibm Aix

Affected Assets

ibm
db2 high performance unload load
6.1.0.1, 6.1.0.2, 6.1.0.3, 6.5.0.0 · 5.1.0.0 — 6.1.0.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer security testing and code review can discover incorrect buffer-size computations before deployment.

Secure engineering principles directly require correct buffer-size arithmetic and bounds-checked allocation.

Input validation can enforce that supplied lengths or counts used in size calculations are within safe bounds.

Memory-protection mechanisms limit the exploitability of an overflow that results from an incorrect size calculation.

Flaw-remediation processes that include vulnerability scanning or static analysis will surface buffer-size errors.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent buffer-size miscalculations via coding standards, reviews, and testing, while fixing this single weakness only partially fulfills the broader control.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Secure coding standards directly require correct buffer-size calculations.

finds

Security testing can detect buffer-size errors before release.

prevents

Secure development lifecycle mandates size-checking practices that reduce buffer-size miscalculations.

prevents

Application security requirements can specify buffer-size validation rules.

prevents

Secure architecture principles include safe memory-allocation guidelines.

References