IBM
Informix Dynamic Server
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
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-13476 | 12 Aug 2026 | 14.10; 15.0; 12.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-13367 | 12 Aug 2026 | 14.10; 15.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-13361 | 12 Aug 2026 | 14.10; 12.10.x; 15.0 | 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-2024-45675 | 2 Dec 2025 | Informix Dynamic Server: 14.10 | Remediation/Fixes Impact is limited to Informix Server on Windows. No exploitation has been observed or is possible on non‑Windows platforms. Update to IBM Informix Dynamic Server 14.10.xC11W1. Fix is available on IBM Fix Central - Select Fixes - Informix Server . Follow the instructions for Database server upgrades in the Informix Servers documentation Follow the instructions to install or upgrade Informix in the What's new and changed in Informix in the IBM Cloud Pak for Data documentation. | Update reference ↗ |
| CVE-2024-49343 | 28 Jul 2025 | 12.10; 14.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-49342 | 28 Jul 2025 | 12.10; 14.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1991 | 28 Jun 2025 | 12.10; 14.10; 15.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-28523 | 9 Dec 2023 | 12.10, 14.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-28526 | 9 Dec 2023 | 12.10, 14.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-28527 | 9 Dec 2023 | 12.10, 14.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-20515 | 30 Apr 2021 | 14.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-2020-4799 | 8 Oct 2020 | 14.10 | 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.