← Search results
CVE-LINKED INVENTORY135 SECURITY RECORDS
IBM Corporation
Sterling B2B Integrator
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-19273 | 14 Sep 2026 | Sterling B2B Integrator: 6.2.0.0 ≤ 6.2.0.6_2, 6.2.1.0 - 6.2.1.2, 6.2.2.0 - 6.2.2.1; Sterling File Gateway: 6.2.0.0 ≤ 6.2.0.6_2, 6.2.1.0 - 6.2.1.2, 6.2.2.0 - 6.2.2.1 | ProductVersionAPARRemediation & FixIBM Sterling B2B Integrator6.2.0.0 - 6.2.0.6_2, 6.2.1.0 - 6.2.1.2, 6.2.2.0 - 6.2.2.1IT49630Apply 6.2.1.2_1 or 6.2.2.1_1IBM Sterling File Gateway6.2.0.0 - 6.2.0.6_2, 6.2.1.0 - 6.2.1.2, 6.2.2.0 - 6.2.2.1IT49630Apply 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-b2bi for IBM Sterling B2B Integrator; * cp.icr.io/cp/ibm-sfg for IBM Sterling File Gateway | Update reference ↗ |
| CVE-2025-36431 | 30 Jul 2026 | Sterling B2B Integrator: 6.2.2.0 ≤ 6.2.2.0_1; Sterling File Gateway: 6.2.2.0 ≤ 6.2.2.0_1 | ProductVersionAPARRemediation & FixIBM Sterling B2B Integrator and IBM Sterling File Gateway6.2.2.0 - 6.2.2.0_1 IT49587Apply B2Bi 6.2.2.1; The IIM versions of 6.2.2.1 is available on Fix Central http://www-933.ibm.com/support/fixcentral/swg/selectFixes .; The container version of 6.2.2.1 is available in IBM Entitled Registry. | Update reference ↗ |
| CVE-2025-36298 | 30 Jul 2026 | Sterling B2B Integrator: 6.1.2.0 ≤ 6.1.2.7_2, 6.2.0.0 ≤ 6.2.0.5_2, 6.2.1.0 ≤ 6.2.1.1_2, 6.2.2.0 ≤ 6.2.2.0_1; Sterling File Gateway: 6.1.2.0 ≤ 6.1.2.7_2, 6.2.0.0 ≤ 6.2.0.5_2, 6.2.1.0 ≤ 6.2.1.1_2, 6.2.2.0 ≤ 6.2.2.0_1 | ProductVersionAPARRemediation & FixIBM Sterling B2B Integrator and IBM Sterling File Gateway6.1.2.0 - 6.1.2.7_2 IT48302 Apply B2Bi 6.1.2.8, 6.2.0.6, 6.2.1.2, 6.2.2.1IBM Sterling B2B Integrator and IBM Sterling File Gateway6.2.0.0 - 6.2.0.5_2 IT48302 Apply B2Bi 6.2.0.6, 6.2.1.2, 6.2.2.1IBM Sterling B2B Integrator and IBM Sterling File Gateway6.2.1.0 - 6.2.1.1_2 IT48302 Apply B2Bi 6.2.1.2, 6.2.2.1IBM Sterling B2B Integrator and IBM Sterling File Gateway6.2.2.0 - 6.2.2.0_1 IT48302 Apply B2Bi 6.2.2.1; The IIM versions of 6.1.2.8, 6.2.0.6, 6.2.1.2 and 6.2.2.1 are available on Fix Central http://www-933.ibm.com/support/fixcentral/swg/selectFixes .; The container version of 6.1.2.8, 6.2.0.6, 6.2.1.2 and 6.2.2.1 are available in IBM Entitled Registry. | Update reference ↗ |
| CVE-2026-1918 | 28 Jul 2026 | 6.2.0.0 ≤ 6.2.0.5_2; 6.2.1.0 ≤ 6.2.1.1_2; 6.2.2.0 ≤ 6.2.2.0_1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-3157 | 28 Jul 2026 | 6.2.0.0 ≤ 6.2.0.5_2; 6.2.1.0 ≤ 6.2.1.1_2; 6.2.2.0 ≤ 6.2.2.0_1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-3158 | 28 Jul 2026 | 6.2.0.0 ≤ 6.2.0.5_2; 6.2.1.0 ≤ 6.2.1.1_2; 6.2.2.0 ≤ 6.2.2.0_1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-7362 | 28 Jul 2026 | 6.2.1.0 ≤ 6.2.1.1_2; 6.2.2.0 ≤ 6.2.2.0_1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-7769 | 28 Jul 2026 | 6.2.0.0 ≤ 6.2.0.5_2; 6.2.1.0 ≤ 6.2.1.1_2; 6.2.2.0 ≤ 6.2.2.0_1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-7775 | 28 Jul 2026 | 6.2.0.0 ≤ 6.2.0.6; 6.2.1.0 ≤ 6.2.1.1_2; 6.2.2.0 ≤ 6.2.2.0_1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-3482 | 22 Jul 2026 | 6.2.0.0 ≤ 6.2.0.5_2; 6.2.1.0 ≤ 6.2.1.1_2; 6.2.2.0 ≤ 6.2.2.0_1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-7253 | 22 Jun 2026 | 6.2.1.0 ≤ 6.2.1.1_2; 6.2.2.0 ≤ 6.2.2.0_1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-1264 | 17 Mar 2026 | 6.1.0.0 ≤ 6.1.2.7_2; 6.2.0.0 ≤ 6.2.0.5_1; 6.2.1.0 ≤ 6.2.1.1_1; 6.2.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-14031 | 17 Mar 2026 | 6.1.0.0 ≤ 6.1.2.7_2; 6.2.0.0 ≤ 6.2.0.5_1; 6.2.1.0 ≤ 6.2.1.1_1; 6.2.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36368 | 13 Mar 2026 | 6.1.0.0 ≤ 6.1.2.7_2; 6.2.0.0 ≤ 6.2.0.5_1; 6.2.1.0 ≤ 6.2.1.1_1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-40693 | 13 Mar 2026 | 6.1.0.0 ≤ 6.1.2.7_2; 6.2.0.0 ≤ 6.2.0.5_1; 6.2.1.0 ≤ 6.2.1.1_1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-14483 | 13 Mar 2026 | 6.1.0.0 ≤ 6.1.2.7_2; 6.2.0.0 ≤ 6.2.0.5_1; 6.2.1.0 ≤ 6.2.1.1_1; 6.2.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-14504 | 13 Mar 2026 | 6.1.0.0 ≤ 6.1.2.7_2; 6.2.0.0 ≤ 6.2.0.5_1; 6.2.1.0 ≤ 6.2.1.1_1; 6.2.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-0835 | 13 Mar 2026 | 6.1.0.0 ≤ 6.1.2.7_2; 6.2.0.0 ≤ 6.2.0.5_1; 6.2.1.0 ≤ 6.2.1.1_1; 6.2.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36348 | 17 Feb 2026 | 6.1.0.0 ≤ 6.1.2.7_2; 6.2.0.0 ≤ 6.2.0.5; 6.2.1.0 ≤ 6.2.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36134 | 25 Nov 2025 | 6.0.0.0 ≤ 6.1.2.7; 6.2.0.0 ≤ 6.2.0.5; 6.2.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36112 | 24 Nov 2025 | 6.0.0.0 ≤ 6.1.2.7; 6.2.0.0 ≤ 6.2.0.5; 6.2.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36135 | 7 Nov 2025 | 6.0.0.0 ≤ 6.1.2.7_1; 6.2.0.0 ≤ 6.2.0.5; 6.2.1.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36002 | 16 Oct 2025 | 6.2.0.0 ≤ 6.2.0.5; 6.2.1.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-2667 | 4 Sep 2025 | 6.0.0.0 ≤ 6.1.2.7_1; 6.2.0.0 ≤ 6.2.0.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-2694 | 4 Sep 2025 | 6.0.0.0 ≤ 6.1.2.7_1; 6.2.0.0 ≤ 6.2.0.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-2988 | 19 Aug 2025 | 6.0.0.0 ≤ 6.1.2.7; 6.2.0.0 ≤ 6.2.0.4; 6.2.1.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-33008 | 19 Aug 2025 | 6.2.1.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-33014 | 18 Jul 2025 | 6.0.0.0 ≤ 6.1.2.7; 6.2.0.0 ≤ 6.2.0.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-2793 | 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-2025-3630 | 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-2025-1349 | 18 Jun 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-2025-1348 | 18 Jun 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-54172 | 18 Jun 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-54183 | 18 Jun 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-47116 | 31 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-2024-45089 | 31 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-2024-49807 | 31 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-2024-40696 | 31 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-2024-47103 | 31 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-38739 | 31 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-50316 | 28 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-27263 | 28 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-2021-20553 | 18 Dec 2024 | 5.2.0.0 ≤ 5.2.6.5; 6.0.0.0 ≤ 6.0.0.6; 6.0.1.0 ≤ 6.0.3.4; 6.1.0.0 ≤ 6.1.0.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-45186 | 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-2023-50307 | 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-2024-22357 | 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-2023-42016 | 9 Feb 2024 | 6.0.0.0 ≤ 6.0.3.8; 6.1.0.0 ≤ 6.1.2.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-2023-32341 | 9 Feb 2024 | 6.0.0.0 ≤ 6.0.3.8; 6.1.0.0 ≤ 6.1.2.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-2022-35638 | 22 Nov 2023 | 6.0.0.0 ≤ 6.0.3.8; 6.1.0.0 ≤ 6.1.2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-22876 | 15 Mar 2023 | 6.0.0.0 < 6.0.3.7; 6.1.0.0 < 6.1.2.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.