CVE-2025-1348: IBM Sterling B2B Integrator · Information Exposure Through Browser Caching
Affects IBM Sterling B2B IntegratorSource CVE Database V5
Not known to be exploited · CVSS 4.0 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Jun 2025
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 |
|---|---|---|
| IBM Sterling B2B Integrator | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Immediately review and update the caching policies on the web servers hosting IBM Sterling B2B Integrator interfaces to ensure that sensitive pages include appropriate HTTP headers such as 'Cache-Control: no-store, no-cache, must-revalidate' and 'Pragma: no-cache' to prevent browser caching of sensitive content. 2) Restrict local access to systems used to access Sterling B2B Integrator by enforcing strict endpoint security controls, including user authentication, session timeouts, and screen locking. 3) Educate users about the risks of leaving browsers open on shared or public machines and encourage the use of private/incognito browsing modes when accessing sensitive systems. 4) Monitor and audit local access logs for unusual activity that could indicate attempts to access cached data. 5) Apply any forthcoming patches or updates from IBM promptly once available. 6) Consider deploying endpoint security solutions that can detect and prevent unauthorized access to browser cache files or sensitive data remnants. 7) If feasible, isolate Sterling B2B Integrator access to dedicated, hardened workstations with minimal local user privileges to reduce the attack surface.
Description
IBM Sterling B2B Integrator and IBM Sterling File Gateway 6.0.0.0 through 6.1.2.6 and 6.2.0.0 through 6.2.0.4 could allow a local user to obtain sensitive information from a user’s web browser cache due to not using a suitable caching policy.