CVE-2025-36065: IBM Sterling Connect:Express Adapter for Sterling B2B Integrator 5.2.0 · Insufficient Session Expiration
Affects IBM Sterling Connect:Express Adapter for Sterling B2B Integrator 5.2.0Source CVE Database V5
Not known to be exploited · CVSS 6.3 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 20 Jan 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMSterling Connect:Express Adapter for Sterling B2B Integrator 5.2.0 | Affected
| Fixed in– |
Mavencom.ibm/sterling-connect-express-adapterpkg:maven/com.ibm/sterling-connect-express-adapterOther threats | Affected
| Fixed in– |
CPE configurations (2)
cpe:2.3:a:ibm:sterling_connectexpress_adapter_for_sterling_b2b_integrator_520:5.2.0.00:*:*:*:*:*:*:*cpe:2.3:a:ibm:sterling_connectexpress_adapter_for_sterling_b2b_integrator_520:5.2.0.12:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Implement strict session management policies that enforce session invalidation upon browser closure or after a short inactivity timeout, even if the software does not do so by default.
- Configure web application firewalls (WAFs) or reverse proxies to detect and block suspicious session reuse or anomalies in session tokens.
- Require multi-factor authentication (MFA) for accessing the Sterling B2B Integrator interface to reduce the risk of session hijacking.
- Regularly audit and monitor session logs for unusual activity, such as concurrent sessions from different IP addresses or geographic locations.
- Educate users to log out explicitly rather than relying on browser closure to terminate sessions.
- Isolate Sterling B2B Integrator access to trusted networks and restrict administrative access via VPN or zero-trust network access solutions.
- Engage with IBM support for any available patches or updates and plan for timely application once released.
- Consider deploying endpoint security controls to prevent session token theft from client machines.
- Review and harden session cookie attributes (e.g., Secure, HttpOnly, SameSite) to reduce the risk of token theft via cross-site scripting or network interception.
Description
IBM Sterling Connect:Express Adapter for Sterling B2B Integrator 5.2.0 5.2.0.00 through 5.2.0.12 does not invalidate session after a browser closure which could allow an authenticated user to impersonate another user on the system.