← Search results
CVE-LINKED INVENTORY48 SECURITY RECORDS
IBM
DB2
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record IBM Db2. Use that record for publisher support phases and retirement dates.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-15955 | 14 Sep 2026 | Db2: 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.5 | Customers running any vulnerable affected level of an affected Program, V11.5, and V12.1, can download the security update containing the interim fix for this issue from Fix Central. These security updates are available based on the most recent level for each impacted release: V11.5.9, V12.1.4, and V12.1.5. They can be applied to any affected level of the appropriate release to remediate this vulnerability.; ReleaseFixed in mod packAPARDownload URLV11.5TBD https://www.ibm.com/support/pages/node/7087189 V12.1TBD https://www.ibm.com/support/pages/node/7267513; Security Update #89304 or later for V12.1.5 available at this link:; https://www.ibm.com/support/pages/node/7282633; IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. | Update reference ↗ |
| CVE-2026-16702 | 14 Sep 2026 | Db2: 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.5 | Customers running any vulnerable affected level of an affected Program, V11.5, and V12.1, can download the security update containing the interim fix for this issue from Fix Central. These security updates are available based on the most recent level for each impacted release: V11.5.9, V12.1.4, and V12.1.5. They can be applied to any affected level of the appropriate release to remediate this vulnerability.; ReleaseFixed in mod packAPARDownload URLV11.5TBD https://www.ibm.com/support/pages/node/7087189 V12.1TBD https://www.ibm.com/support/pages/node/7267513; Security Update #89304 or later for V12.1.5 available at this link:; https://www.ibm.com/support/pages/node/7282633; IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. | Update reference ↗ |
| CVE-2026-17463 | 14 Sep 2026 | Db2: 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.5 | Customers running any vulnerable affected level of an affected Program, V11.5, and V12.1, can download the security update containing the interim fix for this issue from Fix Central. These security updates are available based on the most recent level for each impacted release: V11.5.9, V12.1.4, and V12.1.5. They can be applied to any affected level of the appropriate release to remediate this vulnerability.; ReleaseFixed in mod packAPARDownload URLV11.5TBD https://www.ibm.com/support/pages/node/7087189 V12.1TBD https://www.ibm.com/support/pages/node/7267513; Security Update #89304 or later for V12.1.5 available at this link:; https://www.ibm.com/support/pages/node/7282633; IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. | Update reference ↗ |
| CVE-2026-86087 | 10 Sep 2026 | Db2: 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.5 | Customers running any vulnerable affected level of an affected Program, V11.5, and V12.1, can download the security update containing the interim fix for this issue from Fix Central. These security updates are available based on the most recent level for each impacted release: V11.5.9, V12.1.4, and V12.1.5. They can be applied to any affected level of the appropriate release to remediate this vulnerability.; ReleaseFixed in mod packAPARDownload URLV11.5TBD https://www.ibm.com/support/pages/node/7087189 V12.1TBD https://www.ibm.com/support/pages/node/7267513; Security Update #89304 or later for V12.1.5 available at this link:; https://www.ibm.com/support/pages/node/7282633; IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. | Update reference ↗ |
| CVE-2026-86093 | 10 Sep 2026 | Db2: 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.5 | Customers running any vulnerable affected level of an affected Program, V11.5, and V12.1, can download the security update containing the interim fix for this issue from Fix Central. These security updates are available based on the most recent level for each impacted release: V11.5.9, V12.1.4, and V12.1.5. They can be applied to any affected level of the appropriate release to remediate this vulnerability.; ReleaseFixed in mod packAPARDownload URLV11.5TBD https://www.ibm.com/support/pages/node/7087189 V12.1TBD https://www.ibm.com/support/pages/node/7267513; Security Update #89304 or later for V12.1.5 available at this link:; https://www.ibm.com/support/pages/node/7282633; IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. | Update reference ↗ |
| CVE-2026-87958 | 10 Sep 2026 | Db2: 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.5 | Customers running any vulnerable affected level of an affected Program, V11.5, and V12.1, can download the security update containing the interim fix for this issue from Fix Central. These security updates are available based on the most recent level for each impacted release: V11.5.9, V12.1.4, and V12.1.5. They can be applied to any affected level of the appropriate release to remediate this vulnerability.; ReleaseFixed in mod packAPARDownload URLV11.5TBD https://www.ibm.com/support/pages/node/7087189 V12.1TBD https://www.ibm.com/support/pages/node/7267513; Security Update #89304 or later for V12.1.5 available at this link:; https://www.ibm.com/support/pages/node/7282633; IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. | Update reference ↗ |
| CVE-2026-10534 | 12 Aug 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-10543 | 12 Aug 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-16480 | 12 Aug 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-18097 | 12 Aug 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-18096 | 12 Aug 2026 | 12.1.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-10535 | 30 Jul 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-10695 | 30 Jul 2026 | 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-7771 | 17 Jul 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-9762 | 17 Jul 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36372 | 30 Jun 2026 | Db2: 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.4 | Customers running any vulnerable affected level of an affected Program, V11.5, and V12.1, can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent level for each impacted release: V11.5.9, and V12.1.4. They can be applied to any affected level of the appropriate release to remediate this vulnerability.; ReleaseFixed in mod packAPARDownload URLV11.5TBD https://www.ibm.com/support/pages/node/7087189; V12.1; TBD; https://www.ibm.com/support/pages/node/7267513; IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. | Update reference ↗ |
| CVE-2026-10109 | 30 Jun 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-11906 | 30 Jun 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-6938 | 27 May 2026 | 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-6053 | 27 May 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-6052 | 27 May 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-6051 | 27 May 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-1718 | 27 May 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-13755 | 26 May 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-1577 | 30 Apr 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36122 | 30 Apr 2026 | Db2: 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.3 | Customers running any vulnerable affected level of an affected Program, V11.5, and V12.1, can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent level for each impacted release: V11.5.9. They can be applied to any affected level of the appropriate release to remediate this vulnerability.; ReleaseFixed in mod packAPARDownload URLV11.5TBD https://www.ibm.com/support/pages/node/7087189; V12.1; V12.1.4; https://www.ibm.com/support/pages/node/7267513; Note: To apply this fix, it is required to set DB2_STRICT_INSTANCE_MEMORY=ON in addition to installing the above Special Build.; IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. | Update reference ↗ |
| CVE-2025-14688 | 30 Apr 2026 | Db2: 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.3 | Customers running any vulnerable affected level of an affected Program, V11.5, and V12.1, can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent level for each impacted release: V11.5.9. They can be applied to any affected level of the appropriate release to remediate this vulnerability.; ReleaseFixed in mod packAPARDownload URLV11.5TBD https://www.ibm.com/support/pages/node/7087189; V12.1; V12.1.4; https://www.ibm.com/support/pages/node/7267513; IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. | Update reference ↗ |
| CVE-2026-1352 | 22 Apr 2026 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36006 | 7 Nov 2025 | Db2: 10.5.0 ≤ 10.5.11, 11.1.0 ≤ 11.1.4.7, 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.3 | Remediation/Fixes Customers running any vulnerable affected level of an affected Program, V10.5, V11.1, V11.5, and V12.1, can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent level for each impacted release: V10.5 FP11, V11.1.4 FP7, V11.5.9, V12.1.2 and V12.1.3. They can be applied to any affected level of the appropriate release to remediate this vulnerability. Release Fixed in mod pack APAR Download URL V10.5 TBD DT422191 Special Build for V10.5.11: AIX 64-bit HP-UX 64-bit Linux 32-bit, x86-32 Linux 64-bit, x86-64 Linux 64-bit, POWER™ big endian Linux 64-bit, POWER™ little endian Linux 64-bit, System z®, System z9® or zSeries® Solaris 64-bit, SPARC Solaris 64-bit, x86-64 Windows 32-bit, x86 Windows 64-bit, x86 V11.1 TBD DT422191 Special Build for V11.1.4.7: AIX 64-bit Linux 32-bit, x86-32 Linux 64-bit, x86-64 Linux 64-bit, POWER™ little endian Linux 64-bit, System z®, System z9® or zSeries® Solaris 64-bit, SPARC Windows 32-bit, x86 Windows 64-bit, x86 V11.5 TBD DT422191 Special Build #69673 or later for V11.5.9 available at this link: https://www.ibm.com/support/pages/node/7087189 V12.1 V12.1.3 DT422191 Special Build #70120 or later for V12.1.2 available at this link: https://www.ibm.com/support/pages/db2-v1212-published-cumulative-special-build-downloads IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. Note: After December 31, 2025, 11.1 and 10.5 versions of Db2 will not have security fixes made available as they will reach EoS. | Update reference ↗ |
| CVE-2025-36008 | 7 Nov 2025 | Db2: 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.3 | Remediation/Fixes Customers running any vulnerable affected level of an affected Program, V11.5, and V12.1, can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent level for each impacted release: V11.5.9, V12.1.2 and V12.1.3. They can be applied to any affected level of the appropriate release to remediate this vulnerability. Release Fixed in mod pack APAR Download URL V11.5 TBD DT423510 Special Build #69673 or later for V11.5.9 available at this link: https://www.ibm.com/support/pages/node/7087189 V12.1 V12.1.3 DT423510 Special Build #70120 or later for V12.1.2 available at this link: https://www.ibm.com/support/pages/db2-v1212-published-cumulative-special-build-downloads IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. Note: After December 31, 2025, 11.1 and 10.5 versions of Db2 will not have security fixes made available as they will reach EoS. | Update reference ↗ |
| CVE-2025-36131 | 7 Nov 2025 | Db2: 11.1.0 ≤ 11.1.4.7, 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.3 | Remediation/Fixes Customers running any vulnerable affected level of an affected Program, V11.1, V11.5, and V12.1, can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent level for each impacted release: V11.1.4 FP7, V11.5.9, V12.1.2 and V12.1.3. They can be applied to any affected level of the appropriate release to remediate this vulnerability. Release Fixed in mod pack APAR Download URL V11.1 TBD DT425312 Special Build for V11.1.4.7: AIX 64-bit Linux 32-bit, x86-32 Linux 64-bit, x86-64 Linux 64-bit, POWER™ little endian Linux 64-bit, System z®, System z9® or zSeries® Solaris 64-bit, SPARC Windows 32-bit, x86 Windows 64-bit, x86 V11.5 TBD DT425312 Special Build #69673 or later for V11.5.9 available at this link: https://www.ibm.com/support/pages/node/7087189 V12.1 V12.1.3 DT425312 Special Build #70120 or later for V12.1.2 available at this link: https://www.ibm.com/support/pages/db2-v1212-published-cumulative-special-build-downloads IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. Note: After December 31, 2025, 11.1 and 10.5 versions of Db2 will not have security fixes made available as they will reach EoS. | Update reference ↗ |
| CVE-2025-36136 | 7 Nov 2025 | Db2: 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.3 | Remediation/Fixes Customers running any vulnerable modpack level of an affected Program, V11.5, and V12.1, can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent level for each impacted release: V11.5.9, V12.1.2 and V12.1.3. They can be applied to any affected level of the appropriate release to remediate this vulnerability. Release Fixed in mod pack APAR Download URL V11.5 TBD DT435369 Special Build #69673 or later for V11.5.9 available at this link: https://www.ibm.com/support/pages/node/7087189 V12.1 V12.1.3 DT435369 Special Build #70120 or later for V12.1.2 available at this link: https://www.ibm.com/support/pages/db2-v1212-published-cumulative-special-build-downloads IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. Note: After December 31, 2025, 11.1 and 10.5 versions of Db2 will not have security fixes made available as they will reach EoS. | Update reference ↗ |
| CVE-2025-36185 | 7 Nov 2025 | Db2: 12.1.0 ≤ 12.1.2 | Remediation/Fixes Customers running any vulnerable affected level of an affected Program, V12.1, can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent level for each impacted release: V12.1.2. They can be applied to any affected level of the appropriate release to remediate this vulnerability. Release Fixed in mod pack APAR Download URL V12.1 NA DT440596 Special Build #70120 or later for V12.1.2 available at this link: https://www.ibm.com/support/pages/db2-v1212-published-cumulative-special-build-downloads IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. Note: After December 31, 2025, 11.1 and 10.5 versions of Db2 will not have security fixes made available as they will reach EoS. | Update reference ↗ |
| CVE-2025-36186 | 7 Nov 2025 | Db2: 12.1.0 ≤ 12.1.3 | Remediation/Fixes Customers running any vulnerable affected level of an affected Program, V12.1, can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent level for each impacted release: V12.1.2 and V12.1.3. They can be applied to any affected level of the appropriate release to remediate this vulnerability. Release Fixed in mod pack APAR Download URL V12.1 V12.1.3 DT445866 Special Build #70120 or later for V12.1.2 available at this link: https://www.ibm.com/support/pages/db2-v1212-published-cumulative-special-build-downloads IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. Note: After December 31, 2025, 11.1 and 10.5 versions of Db2 will not have security fixes made available as they will reach EoS. | Update reference ↗ |
| CVE-2025-33012 | 7 Nov 2025 | Db2: 10.5.0 ≤ 10.5.11, 11.1.0 ≤ 11.1.4.7, 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.3 | Remediation/Fixes Customers running any vulnerable affected level of an affected Program, V10.5, V11.1, V11.5, and V12.1, can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent level for each impacted release: V10.5 FP11, V11.1.4 FP7, V11.5.9, V12.1.2 and V12.1.3. They can be applied to any affected level of the appropriate release to remediate this vulnerability. Release Fixed in mod pack APAR Download URL V10.5 TBD DT435638 Special Build for V10.5.11: AIX 64-bit HP-UX 64-bit Linux 32-bit, x86-32 Linux 64-bit, x86-64 Linux 64-bit, POWER™ big endian Linux 64-bit, POWER™ little endian Linux 64-bit, System z®, System z9® or zSeries® Solaris 64-bit, SPARC Solaris 64-bit, x86-64 Windows 32-bit, x86 Windows 64-bit, x86 V11.1 TBD DT435638 Special Build for V11.1.4.7: AIX 64-bit Linux 32-bit, x86-32 Linux 64-bit, x86-64 Linux 64-bit, POWER™ little endian Linux 64-bit, System z®, System z9® or zSeries® Solaris 64-bit, SPARC Windows 32-bit, x86 Windows 64-bit, x86 V11.5 TBD DT435638 Special Build #69673 or later for V11.5.9 available at this link: https://www.ibm.com/support/pages/node/7087189 V12.1 V12.1.3 DT435638 Special Build #70120 or later for V12.1.2 available at this link: https://www.ibm.com/support/pages/db2-v1212-published-cumulative-special-build-downloads IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. Note: After December 31, 2025, 11.1 and 10.5 versions of Db2 will not have security fixes made available as they will reach EoS. | Update reference ↗ |
| CVE-2025-2534 | 7 Nov 2025 | Db2: 11.1.0 ≤ 11.1.4.7, 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.3 | Remediation/Fixes Customers running any vulnerable affected level of an affected Program, V11.1, V11.5, and V12.1, can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent level for each impacted release: V11.1.4 FP7, V11.5.9, V12.1.2 and V12.1.3. They can be applied to any affected level of the appropriate release to remediate this vulnerability. Release Fixed in mod pack APAR Download URL V11.1 TBD DT422178 Special Build for V11.1.4.7: AIX 64-bit Linux 32-bit, x86-32 Linux 64-bit, x86-64 Linux 64-bit, POWER™ little endian Linux 64-bit, System z®, System z9® or zSeries® Solaris 64-bit, SPARC Windows 32-bit, x86 Windows 64-bit, x86 V11.5 TBD DT422178 Special Build #69673 or later for V11.5.9 available at this link: https://www.ibm.com/support/pages/node/7087189 V12.1 V12.1.3 DT422178 Special Build #70120 or later for V12.1.2 available at this link: https://www.ibm.com/support/pages/db2-v1212-published-cumulative-special-build-downloads IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. Note: After December 31, 2025, 11.1 and 10.5 versions of Db2 will not have security fixes made available as they will reach EoS. | Update reference ↗ |
| CVE-2024-47118 | 7 Nov 2025 | Db2: 10.5.0 ≤ 10.5.11, 11.1.0 ≤ 11.1.4.7, 11.5.0 ≤ 11.5.9, 12.1.0 ≤ 12.1.3 | Remediation/Fixes Customers running any vulnerable affected level of an affected Program, V10.5, V11.1, V11.5, and V12.1, can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent level for each impacted release: V10.5 FP11, V11.1.4 FP7, V11.5.9, V12.1.2 and V12.1.3. They can be applied to any affected level of the appropriate release to remediate this vulnerability. Release Fixed in mod pack APAR Download URL V10.5 TBD DT398093 Special Build for V10.5.11: AIX 64-bit HP-UX 64-bit Linux 32-bit, x86-32 Linux 64-bit, x86-64 Linux 64-bit, POWER™ big endian Linux 64-bit, POWER™ little endian Linux 64-bit, System z®, System z9® or zSeries® Solaris 64-bit, SPARC Solaris 64-bit, x86-64 Windows 32-bit, x86 Windows 64-bit, x86 V11.1 TBD DT398093 Special Build for V11.1.4.7: AIX 64-bit Linux 32-bit, x86-32 Linux 64-bit, x86-64 Linux 64-bit, POWER™ little endian Linux 64-bit, System z®, System z9® or zSeries® Solaris 64-bit, SPARC Windows 32-bit, x86 Windows 64-bit, x86 V11.5 TBD DT398093 Special Build #69673 or later for V11.5.9 available at this link: https://www.ibm.com/support/pages/node/7087189 V12.1 V12.1.3 DT398093 Special Build #70120 or later for V12.1.2 available at this link: https://www.ibm.com/support/pages/db2-v1212-published-cumulative-special-build-downloads IBM does not disclose key Db2 functionality nor replication steps for a vulnerability to avoid providing too much information to any potential malicious attacker. IBM does not want to enable a malicious attacker with sufficient knowledge to craft an exploit of the vulnerability. Note: After December 31, 2025, 11.1 and 10.5 versions of Db2 will not have security fixes made available as they will reach EoS. | Update reference ↗ |
| CVE-2024-49828 | 29 Jul 2025 | 10.5.0.0 ≤ 10.5.0.11; 11.1.0 ≤ 11.1.4.7; 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-51473 | 29 Jul 2025 | 10.5.0.0 ≤ 10.5.0.11; 11.1.0 ≤ 11.1.4.7; 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-52894 | 29 Jul 2025 | 10.5.0.0 ≤ 10.5.0.11; 11.1.0 ≤ 11.1.4.7; 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-33114 | 29 Jul 2025 | 12.1.0; 12.1.1; 12.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-33092 | 29 Jul 2025 | 11.5.0 ≤ 11.5.9; 12.1.0 ≤ 12.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36010 | 29 Jul 2025 | 12.1.0; 12.1.1; 12.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-2533 | 29 Jul 2025 | 12.1.0; 12.1.1; 12.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-40679 | 8 Jan 2025 | 11.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-47145 | 7 Jan 2024 | 10.5, 11.1, 11.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-4014 | 3 Apr 2019 | 9.7; 10.1; 10.5; 11.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-1936 | 3 Apr 2019 | 9.7; 10.1; 10.5; 11.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.