VulnerabilityPublished 17 Feb 2026

CVE-2025-36348: IBM Sterling B2B Integrator · Generation of Error Message Containing Sensitive Information

Affects IBM Sterling B2B IntegratorSource CVE Database V5

Not known to be exploited · CVSS 4.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBMSterling B2B Integrator	Affected >=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	Fixed in–
IBMSterling File Gateway	Affected >=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	Fixed in–

CPE configurations (12)

cpe:2.3:a:ibm:sterling_b2b_integrator:6.1.0.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:sterling_b2b_integrator:6.1.2.7_2:*:*:*:*:*:*:*
cpe:2.3:a:ibm:sterling_b2b_integrator:6.2.0.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:sterling_b2b_integrator:6.2.0.5:*:*:*:*:*:*:*
cpe:2.3:a:ibm:sterling_b2b_integrator:6.2.1.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:sterling_b2b_integrator:6.2.1.1:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2025-36348, organizations should implement the following specific measures: 1) Configure IBM Sterling B2B Integrator and File Gateway to suppress detailed error messages in production environments, ensuring that only generic error information is displayed to users or remote clients. 2) Restrict access to administrative interfaces and error reporting pages to trusted internal networks or VPNs to limit exposure to privileged attackers. 3) Monitor application logs and network traffic for unusual access patterns or attempts to trigger error messages that could indicate reconnaissance activity. 4) Apply any IBM-provided patches or updates as soon as they become available to address this vulnerability directly. 5) Conduct regular security assessments and penetration tests focusing on error handling and information leakage in these applications. 6) Educate system administrators and developers on secure error handling best practices to avoid exposing sensitive information in future deployments. These targeted actions go beyond generic advice by focusing on error message management, access control, and proactive monitoring specific to the affected IBM products.

Description

IBM Sterling B2B Integrator versions 6.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5, and 6.2.1.0 through 6.2.1.1, and IBM Sterling File Gateway versions 6.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5, and 6.2.1.0 through 6.2.1.1 may expose sensitive information to a remote privileged attacker due to the application returning detailed technical error messages in the browser.

Impact

The primary impact of CVE-2025-36348 is the exposure of sensitive internal information to remote privileged attackers, which can facilitate further attacks such as privilege escalation, targeted exploitation, or lateral movement within the network. Although the vulnerability does not directly compromise system integrity or availability, the leakage of detailed error messages can reveal system architecture, software versions, and configuration details that attackers can leverage to identify additional vulnerabilities or misconfigurations. This can increase the attack surface and risk of more severe breaches. Organizations relying on IBM Sterling B2B Integrator and File Gateway for critical business-to-business transactions and file transfers may face increased risk of data breaches or operational disruptions if attackers exploit this information disclosure. The medium severity rating indicates a moderate risk that should be addressed promptly to maintain confidentiality and reduce attack vectors.

CWE-209Generation of Error Message Containing Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product generates an error message that includes sensitive information about its environment, users, or associated data.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
Implementation
Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
Implementation · Attack Surface Reduction
Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
Padding Oracle Crypto Attack (opens in a new tab)
Query System for Information (opens in a new tab)
Blind SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7259769 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (12)

Description

AI analysisMachine-generated, updated 25 Feb 2026, 00:10 UTC

WeaknessesCWE-209

Technical details

References

Community reviews

Related threats