Skip to main content
VulnerabilityPublished

CVE-2025-14031: IBM Sterling B2B Integrator · Command Injection

Affects IBM Sterling B2B IntegratorSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBMSterling B2B IntegratorAffected
  • >=6.1.0.0 <=6.1.2.7_2
  • >=6.2.0.0 <=6.2.0.5_1
  • >=6.2.1.0 <=6.2.1.1_1
  • =6.2.2.0
Fixed in–

CPE configurations (7)

  • 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_1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:sterling_b2b_integrator:6.2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:sterling_b2b_integrator:6.2.1.1_1:*:*:*:*:*:*:*

AI-suggested

Organizations should immediately identify and inventory all instances of IBM Sterling B2B Integrator and IBM Sterling File Gateway within their environment to determine exposure. Implementing strict input validation and sanitization on all user-supplied data that interacts with system commands can help mitigate injection risks. Network-level protections including web application firewalls (WAFs) configured to detect and block command injection patterns should be deployed. Monitoring and alerting for unusual application crashes or malformed requests can provide early detection of exploitation attempts. Organizations should maintain up-to-date backups and incident response plans to quickly recover from potential denial of service events. Once IBM releases official patches, prompt application is critical to fully remediate the vulnerability.

Description

IBM Sterling B2B Integrator and and IBM Sterling File Gateway 6.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5_1, 6.2.1.0 through 6.2.1.1_1, and 6.2.2.0 could allow an unauthenticated attacker to send a specially crafted request that causes the application to crash.

References

Community reviews

Loading reviews…