What's new and changed in Db2

Db2 updates can include new features and fixes. Releases are listed in reverse chronological order so that the latest release is at the beginning of the topic.

You can see a list of the new features for the platform and all of the services at What's new in IBM Software Hub.

Installing or upgrading Db2

Ready to install or upgrade Db2?

To install Db2 along with the other IBM® Software Hub services, see Installing IBM Software Hub.
To upgrade Db2 along with the other IBM Software Hub services, see Upgrading IBM Software Hub.
To install or upgrade Db2 independently, see Db2.
Remember: All of the IBM Software Hub components associated with an instance of IBM Software Hub must be installed at the same version.

IBM Software Hub Version 5.3.1

A new version of Db2 was released in February 2026 with IBM Software Hub 5.3.1.

Operand version: 5.3.1

This release includes the following changes:

Security issues fixed in this release

The following security issues were fixed in this release:

CVE-2026-24049, CVE-2026-23949, CVE-2026-23490, CVE-2026-21441

CVE-2025-9714, CVE-2025-9230, CVE-2025-8869, CVE-2025-8291, CVE-2025-6965, CVE-2025-69277, CVE-2025-68973, CVE-2025-68287, CVE-2025-68285, CVE-2025-66506, CVE-2025-66471, CVE-2025-66418, CVE-2025-66293, CVE-2025-65018, CVE-2025-64720, CVE-2025-64329, CVE-2025-61985, CVE-2025-61984, CVE-2025-61912, CVE-2025-61911, CVE-2025-61729, CVE-2025-61727, CVE-2025-61725, CVE-2025-61724, CVE-2025-61723, CVE-2025-61594, CVE-2025-6075, CVE-2025-6069, CVE-2025-59375, CVE-2025-59250, CVE-2025-58457, CVE-2025-58189, CVE-2025-58185, CVE-2025-58183, CVE-2025-58058, CVE-2025-55199, CVE-2025-55198, CVE-2025-54410, CVE-2025-53906, CVE-2025-53905, CVE-2025-52881, CVE-2025-52565, CVE-2025-5187, CVE-2025-50181, CVE-2025-48964, CVE-2025-47912, CVE-2025-47906, CVE-2025-4673, CVE-2025-4598, CVE-2025-45582, CVE-2025-41249, CVE-2025-40909, CVE-2025-40780, CVE-2025-40778, CVE-2025-40300, CVE-2025-40277, CVE-2025-40185, CVE-2025-40176, CVE-2025-40058, CVE-2025-39981, CVE-2025-39979, CVE-2025-39966, CVE-2025-39955, CVE-2025-39925, CVE-2025-39918, CVE-2025-39864, CVE-2025-39849, CVE-2025-39843, CVE-2025-39841, CVE-2025-39819, CVE-2025-39817, CVE-2025-39730, CVE-2025-39718, CVE-2025-39702, CVE-2025-38724, CVE-2025-38703, CVE-2025-38571, CVE-2025-38566, CVE-2025-38396, CVE-2025-38116, CVE-2025-37994, CVE-2025-31133, CVE-2025-30698, CVE-2025-30691, CVE-2025-22874, CVE-2025-22872, CVE-2025-22871, CVE-2025-22870, CVE-2025-22869, CVE-2025-22868, CVE-2025-22866, CVE-2025-22097, CVE-2025-22056, CVE-2025-21864, CVE-2025-21863, CVE-2025-21861, CVE-2025-21855, CVE-2025-21853, CVE-2025-21851, CVE-2025-21848, CVE-2025-21846, CVE-2025-21844, CVE-2025-21839, CVE-2025-21829, CVE-2025-21828, CVE-2025-21826, CVE-2025-21806, CVE-2025-21796, CVE-2025-21795, CVE-2025-21791, CVE-2025-21790, CVE-2025-21787, CVE-2025-21786, CVE-2025-21765, CVE-2025-21746, CVE-2025-21745, CVE-2025-21739, CVE-2025-21738, CVE-2025-21729, CVE-2025-21728, CVE-2025-21726, CVE-2025-21714, CVE-2025-21702, CVE-2025-21696, CVE-2025-21693, CVE-2025-21691, CVE-2025-21672, CVE-2025-21671, CVE-2025-21648, CVE-2025-21647, CVE-2025-21631, CVE-2025-21614, CVE-2025-21613, CVE-2025-15284, CVE-2025-13601, CVE-2025-11561, CVE-2025-11083, CVE-2025-0426

CVE-2024-58088, CVE-2024-58083, CVE-2024-58075, CVE-2024-58072, CVE-2024-58062, CVE-2024-58057, CVE-2024-58015, CVE-2024-58014, CVE-2024-57998, CVE-2024-57995, CVE-2024-57990, CVE-2024-57989, CVE-2024-57988, CVE-2024-57987, CVE-2024-57986, CVE-2024-57981, CVE-2024-58012, CVE-2024-58068, CVE-2024-58077, CVE-2024-56739, CVE-2024-56709, CVE-2024-56690, CVE-2024-56675, CVE-2024-56672, CVE-2024-56662, CVE-2024-56645, CVE-2024-56603, CVE-2024-5642, CVE-2024-53241, CVE-2024-53229, CVE-2024-53216, CVE-2024-53170, CVE-2024-53135, CVE-2024-53119, CVE-2024-53090, CVE-2024-53052, CVE-2024-52332, CVE-2024-50294, CVE-2024-50195, CVE-2024-50060, CVE-2024-49864, CVE-2024-49761, CVE-2024-49570, CVE-2024-47727, CVE-2024-47679, CVE-2024-46744, CVE-2024-46689, CVE-2024-45341, CVE-2024-45338, CVE-2024-45336, CVE-2024-45310, CVE-2024-43398, CVE-2024-41946, CVE-2024-41123, CVE-2024-39908, CVE-2024-36357, CVE-2024-36350, CVE-2024-36623, CVE-2024-36621, CVE-2024-36620, CVE-2024-34155, CVE-2024-3154, CVE-2024-25621, CVE-2024-21626

CVE-2023-53494, CVE-2023-53373, CVE-2023-53331, CVE-2023-45288, CVE-2023-39804

CVE-2022-50367, CVE-2022-50087, CVE-2022-49845, CVE-2022-49672, CVE-2022-49670, CVE-2022-49657, CVE-2022-49648, CVE-2022-49643, CVE-2022-49627, CVE-2022-49623, CVE-2022-49443, CVE-2022-49437, CVE-2022-49432, CVE-2022-49357, CVE-2022-49353, CVE-2022-49269, CVE-2022-49024, CVE-2022-48830

CVE-2021-43784

IBM Software Hub Version 5.3.0

A new version of Db2 was released in December 2025 with IBM Software Hub 5.3.0.

Operand version: 5.3.0

This release includes the following changes:

New features

This release of Db2 includes the following features:

Deploy Db2 database with non-root deployment (Restricted-v2 SCC)

Now, when deploying a new Db2 database in your IBM Software Hub cluster, you can enable non-root deployment by selecting the checkbox Deploy Db2 with non-root deployment on the Advanced Configurations page. Selecting the Restricted-v2 option uses Red Hat® OpenShift®’s default restricted-v2 Security Context Constraint (SCC) to meet strict security requirements while maintaining full functionality.

This SCC ensures that:

Workloads run with non-root privileges.
Use of sudo or elevated permissions is not allowed.

For more information on permission levels and requirements, see Deploying Db2 with non-root access in a restricted-v2 SCC on IBM Software Hub.

Issues fixed in this release

The following issues were fixed in this release:

Db2 users unable to authenticate to the Db2 OLTP database over JDBC: Issue: When users try to access the Db2 OLTP database via JDBC, they face authentication failures even when they have the admin access.

Security issues fixed in this release

The following security issues were fixed in this release:

CVE-2025-6965, CVE-2025-58754

CVE-2024-6119