How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability none.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- Attack vector: Network — reachable from anywhere that can route to the service.
- Attack complexity: Low — the attack works reliably, with no preparation.
- Privileges required: Low — an ordinary user account is enough.
- User interaction: None — nobody has to be tricked into anything.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
- Integrity impact: None.
- Availability impact: None.
Weakness class
CVE-2026-3158 is classified as CWE-615: Inclusion of Sensitive Information in Source Code Comments. While adding general comments is very useful, some programmers tend to leave important data, such as: filenames related to the web application, old links or links which were not meant to be browsed by users, old code fragments, etc.
Affected software
CVE-2026-3158 is recorded against 2 packages.
- sterling-b2b-integrator (from 6.2.2.0 up to 6.2.2.0_1)
- sterling-file-gateway (from 6.2.2.0 up to 6.2.2.0_1)
Timeline and source
Published on 28 July 2026 and last revised on 3 August 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
www.ibm.com
Other advisories for this package
sterling-b2b-integrator has other advisories on record. If you are patching this one, these are worth checking on the same host:
Same weakness in other software
These advisories are the same class of weakness (CWE-615: Inclusion of Sensitive Information in Source Code Comments) in other software:
