Cyber Resilience

CVE-2025-36348

Info Disclosure in Ibm Sterling B2B Integrator 6.1.0.0 – 6.1.2.8

Published
17 February 2026
Modified
20 February 2026
Patch / advisory
CVSS Score v3.1 4.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0030 22th percentile
Risk Priority 38 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-36348 is a medium-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Ibm Sterling B2B Integrator. Its CVSS base score is 4.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Software (T1592.002); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-11 (Error Handling) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

due to the application returning detailed technical error messages in the browser.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1592.002 Software Reconnaissance
Adversaries may gather information about the victim's host software that can be used during targeting.
T1082 System Information Discovery Discovery
An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture.
T1592 Gather Victim Host Information Reconnaissance
Adversaries may gather information about the victim's hosts that can be used during targeting.
T1595 Active Scanning Reconnaissance
Adversaries may execute active reconnaissance scans to gather information that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-2667Same product: Ibm Sterling B2B Integrator
CVE-2025-36112Same product: Ibm Sterling B2B Integrator
CVE-2025-2988Same product: Ibm Sterling B2B Integrator
CVE-2025-2694Same product: Ibm Sterling B2B Integrator
CVE-2026-0835Same product: Ibm Sterling B2B Integrator
CVE-2025-36135Same product: Ibm Sterling B2B Integrator
CVE-2025-36134Same product: Ibm Sterling B2B Integrator
CVE-2023-40693Same product: Ibm Sterling B2B Integrator
CVE-2026-1264Same product: Ibm Sterling B2B Integrator
CVE-2025-14504Same product: Ibm Sterling B2B Integrator

Affected Assets

ibm
sterling b2b integrator
6.1.0.0 — 6.1.2.8 · 6.2.0.0 — 6.2.0.5_1 · 6.2.1.0 — 6.2.1.1_1
ibm
sterling file gateway
6.1.0.0 — 6.1.2.8 · 6.2.0.0 — 6.2.0.5_1 · 6.2.1.0 — 6.2.1.1_1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V16.5.1

Mitigating Controls (NIST 800-53 r5) AI

si-11 directly requires error messages to avoid revealing exploitable information about the system or its data.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require sanitized error handling to prevent sensitive data disclosure.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards explicitly forbid exposing sensitive data in errors.

finds

Security testing can detect error messages that leak sensitive information.

A.8.15 Logging partial match
degrades

Logging policy can require suppression of sensitive data in error messages.

prevents

Secure SDLC mandates error-handling rules that avoid leaking sensitive information.

prevents

Application security requirements can specify safe error messaging.

prevents

Secure architecture principles include proper exception handling.

References