← Search results
CVE-LINKED INVENTORY42 SECURITY RECORDS
IBM
Sterling File Gateway
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-75878 | 18 Sep 2026 | Sterling File Gateway: 6.2.0.0 ≤ 6.2.0.6_1, 6.2.1.0 - 6.2.1.2, 6.2.2.0 - 6.2.2.1 | IBM strongly recommends addressing the vulnerability now.; Product; VersionAPARRemediation & FixIBM Sterling File Gateway6.2.0.0 - 6.2.0.6_1, 6.2.1.0 - 6.2.1.2, 6.2.2.0 - 6.2.2.1IT49865Apply 6.2.0.6_2, 6.2.1.2_1 or 6.2.2.1_1; The IIM versions 6.2.1.2_1 and 6.2.2.1_1 are available on Fix Central http://www-933.ibm.com/support/fixcentral/swg/selectFixes .; The container versions of 6.2.1.2_1 and 6.2.2.1_1 are available in IBM Entitled Registry; * cp.icr.io/cp/ibm-sfg for IBM Sterling File Gateway; For 6.2.0.6_2, contact the support | Update reference ↗ |
| CVE-2026-19290 | 14 Sep 2026 | Sterling File Gateway: 6.2.0.0 ≤ 6.2.0.6_1, 6.2.1.0 - 6.2.1.2, 6.2.2.0 - 6.2.2.1 | ProductVersionAPARRemediation & FixIBM Sterling File Gateway6.2.0.0 - 6.2.0.6_1, 6.2.1.0 - 6.2.1.2, 6.2.2.0 - 6.2.2.1IT49875Apply 6.2.0.6_2, 6.2.1.2_1 or 6.2.2.1_1; The IIM versions 6.2.1.2_1 and 6.2.2.1_1 are available on Fix Central http://www-933.ibm.com/support/fixcentral/swg/selectFixes .; The container versions of 6.2.1.2_1 and 6.2.2.1_1 are available in IBM Entitled Registry; * cp.icr.io/cp/ibm-sfg for IBM Sterling File Gateway; For 6.2.0.6_2, contact the support | Update reference ↗ |
| CVE-2025-2827 | 8 Jul 2025 | 6.0.0.0 ≤ 6.1.2.6; 6.2.0.0 ≤ 6.2.0.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-47109 | 10 Mar 2025 | 6.0.0.0 ≤ 6.1.2.6; 6.2.0.0 ≤ 6.2.0.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-52292 | 27 Jan 2025 | 6.0.0.0 ≤ 6.1.2.5; 6.2.0.0 ≤ 6.2.0.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-47159 | 27 Jan 2025 | 6.0.0.0 ≤ 6.1.2.5; 6.2.0.0 ≤ 6.2.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-22316 | 27 Jan 2025 | 6.0.0.0 ≤ 6.1.2.5; 6.2.0.0 ≤ 6.2.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-47714 | 12 Apr 2024 | 6.0.0.0 ≤ 6.0.3.9; 6.1.0.0 ≤ 6.1.2.3; 6.2.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-39086 | 16 Aug 2022 | 6.0.0.0; 6.1.0.0; 6.1.1.0; 6.0.3.5; 6.1.0.4; 6.1.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-4654 | 8 Oct 2021 | 2.2.0.0; 6.0.0.0; 5.2.6.5_3; 6.0.3.4; 6.1.0.0; 6.1.0.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-2021-20584 | 7 Oct 2021 | 2.2.0.0; 6.0.1.0; 6.0.0.0; 6.1.0.2; 6.0.0.6; 6.0.3.4; 6.1.0.0; 5.2.6.5_4 | 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-2021-20561 | 7 Oct 2021 | 2.2.0.0; 6.0.1.0; 6.0.0.0; 6.1.0.2; 6.0.0.6; 6.0.3.4; 6.1.0.0; 5.2.6.5_4 | 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-2021-20552 | 7 Oct 2021 | 6.0.1.0; 6.1.0.2 | 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-2021-20489 | 7 Oct 2021 | 2.2.0.0; 6.0.1.0; 6.0.0.0; 6.1.0.3; 5.2.6.5_3; 6.0.0.6; 6.0.3.4; 6.1.0.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-2021-20481 | 7 Oct 2021 | 2.2.0.0; 6.0.1.0; 6.0.0.0; 5.2.6.5_3; 6.0.0.6; 6.0.3.4; 6.1.0.0; 6.1.0.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-2021-20473 | 7 Oct 2021 | 2.2.0.0; 6.0.0.0; 5.2.6.5_3; 6.0.3.4; 6.1.0.0; 6.1.0.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-2021-20376 | 7 Oct 2021 | 2.2.0.0; 6.0.0.0; 5.2.6.5_3; 6.0.3.4; 6.1.0.0; 6.1.0.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-2021-20375 | 7 Oct 2021 | 2.2.0.0; 6.0.0.0; 5.2.6.5_3; 6.0.3.4; 6.1.0.0; 6.1.0.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-2021-20372 | 7 Oct 2021 | 2.2.0.0; 6.0.1.0; 6.0.0.0; 5.2.6.5_3; 6.0.0.6; 6.0.3.4; 6.1.0.0; 6.1.0.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-2021-20563 | 23 Sep 2021 | 2.2.0.0; 6.1.0.3 | 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-2021-20485 | 23 Sep 2021 | 2.2.0.0; 6.1.0.3 | 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-2021-20484 | 23 Sep 2021 | 2.2.0.0; 6.1.0.3 | 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-4658 | 16 Dec 2020 | 2.2.0.0; 6.0.3.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-4763 | 16 Nov 2020 | 2.2.0.0; 6.0.3.2; 2.2.6.5; 6.0.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-4665 | 16 Nov 2020 | 2.2.0.0; 6.0.3.2; 2.2.6.5; 6.0.0.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-2020-4647 | 16 Nov 2020 | 2.2.0.0; 6.0.3.2; 2.2.6.5; 6.0.0.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-2020-4476 | 16 Nov 2020 | 2.2.0.0; 6.0.3.2; 2.2.6.5; 6.0.0.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-2020-4259 | 14 May 2020 | 2.2.0.0; 6.0.3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-4423 | 30 Sep 2019 | 2.2.0.0; 6.0.1.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-4280 | 30 Sep 2019 | 2.2.0.0; 6.0.1.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-4147 | 16 Sep 2019 | 2.2.0.0; 6.0.1.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-2018-1563 | 20 Jul 2018 | 2.2.0; 2.2.6 | 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-1470 | 20 Jul 2018 | 2.2.0; 2.2.6 | 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-1398 | 20 Jul 2018 | 2.2.0; 2.2.6 | 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-2017-1575 | 20 Jul 2018 | 2.2.0; 2.2.6 | 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-2017-1544 | 20 Jul 2018 | 2.2.0; 2.2.6 | 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-2017-1632 | 11 Dec 2017 | 2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-1550 | 11 Dec 2017 | 2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-1549 | 11 Dec 2017 | 2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-1548 | 11 Dec 2017 | 2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-1497 | 7 Dec 2017 | 2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-1487 | 7 Dec 2017 | 2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
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.