dbcve.org
Sterling Connect\Application · Ibm

CVE-2025-36065

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-20
Fix available
A fix is available. Upgrade to 5.2.0.13 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

IBM Sterling Connect:Express Adapter for Sterling B2B Integrator versions 5.2.0.00 through 5.2.0.12 fails to invalidate user sessions upon browser closure. This improper session lifecycle management allows session tokens to remain active, potentially enabling an authenticated attacker to hijack or impersonate other users by reusing stale session credentials.

MitigationUpgrade to a version beyond 5.2.0.12 that implements proper session invalidation on browser closure, or configure the application to enforce session timeouts and immediate token destruction when the browser session ends.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sterling Connect\Application
Affected:>= 5.2.0.00, < 5.2.0.13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine the installed product version
    Locate the product version information for IBM Sterling Connect:Express Adapter. This is typically found in the product's About section, a version file, or by running a version command specific to the installation. Check installation directories for version manifest files or use the product's built-in version reporting mechanism.
    Affected if The installed version is 5.2.0.00 through 5.2.0.12 (any version >= 5.2.0.00 but < 5.2.0.13).
  2. Verify session cookie configuration
    Inspect the application configuration files for session cookie settings. Look for session timeout parameters, session token expiration settings, and whether session cookies are configured with proper expiration (should be 'session' or have an explicit timeout). Check web.xml, IBM-specific configuration files, or the application's session management configuration.
    Affected if Session cookies are not set to expire immediately on browser closure, or there is no explicit session invalidation configured upon logout/browser close.
  3. Check session timeout settings
    Review the session configuration for timeout values. Determine if there is a session timeout defined and what the maximum inactive interval is configured to be. Verify if there are any settings for immediate session invalidation when the browser session ends.
    Affected if Session timeout is set to an excessively long duration or there is no mechanism to invalidate sessions immediately upon browser closure.
  4. Inspect authentication configuration for session lifecycle
    Examine the application's security or authentication configuration files. Look for session management settings that control how sessions are created, maintained, and destroyed. Check if there is any configuration related to session invalidation on logout or browser close events.
    Affected if The configuration lacks proper session invalidation logic that triggers when the browser is closed or the session ends.

You are affected if the installed version of IBM Sterling Connect:Express Adapter falls within 5.2.0.00 to 5.2.0.12 and the session management configuration does not enforce immediate invalidation of session tokens upon browser closure.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.2.0.13 or later
Fixed in 5.2.0.13
Interim mitigation

Upgrade to a version beyond 5.2.0.12 that implements proper session invalidation on browser closure, or configure the application to enforce session timeouts and immediate token destruction when the browser session ends.

Recommended fix High confidence

IBM Sterling Connect:Express Adapter for Sterling B2B Integrator version 5.2.0.13

  1. Identify the current installed version of IBM Sterling Connect:Express Adapter for Sterling B2B Integrator by accessing the product's version information in the administration console or checking the installation directory
  2. Schedule a maintenance window for the upgrade process to minimize business impact
  3. Download the fixed version 5.2.0.13 or later from IBM Fix Central (https://www.ibm.com/support/fixcentral/) or your IBM entitled software repository
  4. Back up the current IBM Sterling Connect:Express Adapter configuration, including any custom settings, adapters, and integration configurations
  5. Stop all IBM Sterling B2B Integrator services and related processes before applying the upgrade
  6. Install the upgrade to version 5.2.0.13 following the IBM installation instructions specific to your deployment topology
  7. After installation, verify the new version number is correctly reported as 5.2.0.13 or higher
  8. Start the IBM Sterling B2B Integrator services and confirm all components are running properly
Caveat Review IBM release notes for 5.2.0.13 for any configuration or behavioral changes that may affect existing integrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sterling Connect\ Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36065 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36065 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data