Quick answers
- Is CVE-2026-3158 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-3158 being exploited in the wild.
- How severe is CVE-2026-3158?
- Medium severity, with a CVSS score of 4.3, published 28 July 2026.
- Which products and versions are affected?
- IBM Sterling File Gateway 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; IBM Sterling B2b Integrator 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.
- Is there a fix for CVE-2026-3158?
- A patch was published on 2026-07-21: Fixes available in versions 6.2.0.6, 6.2.1.2, and 6.2.2.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-3158 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-3158?
- Check whether you run IBM Sterling File Gateway or IBM Sterling B2b Integrator at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is classified as an information disclosure (CWE-615) within the dashboard component of IBM Sterling B2B Integrator and Sterling File Gateway. The root cause is the inclusion of sensitive data within source code comments that are accessible to users. An attacker with low-privileged network access can view these comments to extract sensitive information. The vulnerability affects versions 6.2.0.0 through 6.2.2.0_1. IBM has released patches in versions 6.2.0.6, 6.2.1.2, and 6.2.2.1 to remediate this issue.
Affected products
- IBM Sterling B2B Integrator 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
- IBM Sterling File Gateway 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
Timeline
- 2026-07-21: advisory: Initial publication by IBM
- 2026-07-28: disclosed: NVD publication date
- 2026-07-21: patched: Fixes available in versions 6.2.0.6, 6.2.1.2, and 6.2.2.1