VulnerabilityPublished 5 Feb 2026

CVE-2025-14150: IBM webMethods Integration (on prem) – Integration Server · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects IBM webMethods Integration (on prem) – Integration ServerSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% 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:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Feb 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBMwebMethods Integration (on prem) - Integration Server	Affected =10.15	Fixed in–

CPE configurations (3)

cpe:2.3:a:ibm:webmethods_integration_on_prem___integration_server:10.15:*:*:*:*:*:*:*
cpe:2.3:a:ibm:webmethods_integration_on_prem___integration_server:10.15.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:webmethods_integration_on_prem___integration_server:is_10.15_core_fix2411.1:*:*:*:*:*:*:*

AI-suggested

Organizations should implement the following specific mitigations: 1) Apply IBM patches or updates as soon as they become available for the affected webMethods Integration Server versions. 2) Restrict network access to the Integration Server to trusted internal networks and VPNs, minimizing exposure to untrusted sources. 3) Enforce strict access controls and least privilege principles for users and services interacting with the Integration Server to reduce the chance of privilege abuse. 4) Monitor server logs and network traffic for unusual information disclosure patterns or anomalous requests that could indicate exploitation attempts. 5) Conduct regular security assessments and penetration tests focusing on middleware components to identify potential information leakage. 6) Use web application firewalls (WAFs) or intrusion detection systems (IDS) configured to detect and block suspicious requests targeting the Integration Server. 7) Educate administrators and developers about secure configuration and the risks of information exposure in middleware platforms. These steps go beyond generic advice by focusing on access restriction, monitoring, and proactive detection tailored to the integration environment.

Description

IBM webMethods Integration (on prem) - Integration Server 10.15 through IS_10.15_Core_Fix2411.1 to IS_11.1_Core_Fix8 IBM webMethods Integration could disclose sensitive user information in server responses.

Impact

For European organizations, the exposure of sensitive information in IBM webMethods Integration Server responses can lead to significant confidentiality breaches. Attackers gaining access to such information could leverage it to escalate privileges, conduct targeted attacks, or move laterally within networks. Given the widespread use of IBM webMethods in large enterprises, including financial institutions, manufacturing, and government agencies, the risk extends to critical infrastructure and sensitive data flows. The vulnerability does not directly affect system integrity or availability, so operational disruption is unlikely; however, the leaked information could undermine trust and compliance with data protection regulations such as GDPR. The medium severity rating reflects the balance between the high confidentiality impact and the requirement for some privilege level to exploit. Organizations with exposed or poorly segmented integration servers face higher risk, especially if internal threat actors or compromised accounts are involved.

CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Architecture and Design · Implementation
Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.3.2 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Web Application Fingerprinting (opens in a new tab)
System Location Discovery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7259518 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (3)

Description

AI analysisMachine-generated, updated 5 Feb 2026, 14:29 UTC

WeaknessesCWE-497

Technical details

References

Community reviews

Related threats