CVE-2025-14915: IBM WebSphere Application Server – Liberty · Information Exposure
Affects IBM WebSphere Application Server – LibertySource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMWebSphere Application Server - Liberty | Affected
| Fixed in– |
CPE configurations (2)
cpe:2.3:a:ibm:websphere_application_server___liberty:17.0.0.3:*:*:*:*:*:*:*cpe:2.3:a:ibm:websphere_application_server___liberty:26.0.0.3:*:*:*:*:*:*:*
AI-suggested
Organizations should implement the following specific mitigations: 1) Monitor IBM’s official channels for patches or updates addressing CVE-2025-14915 and apply them promptly once available. 2) Conduct a thorough review of user privileges within WebSphere Application Server - Liberty to ensure the principle of least privilege is enforced, minimizing the number of users with high-level access. 3) Implement strict access controls and multi-factor authentication for administrative accounts to reduce the risk of credential compromise. 4) Enable detailed logging and monitoring of privileged user activities on the application server to detect anomalous behavior indicative of privilege escalation attempts. 5) Segment the network to limit exposure of the WebSphere Application Server to only trusted internal systems and administrators. 6) Regularly audit configuration and access policies to identify and remediate potential privilege escalation vectors. 7) Employ runtime application self-protection (RASP) or Web Application Firewalls (WAF) that can detect and block suspicious requests targeting privilege escalation vulnerabilities. These measures, combined with timely patching, will reduce the risk of exploitation and limit potential damage.
Description
IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.3 IBM WebSphere Application Server Liberty is affected by privilege escalation. A privileged user could gain additional access to the application server.