CVE-2025-36124: IBM WebSphere Application Server Liberty · Privilege Chaining
Affects IBM WebSphere Application Server LibertySource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBM WebSphere Application Server Liberty | Affected
| Fixed in– |
AI-suggested
European organizations should prioritize the following mitigation steps: 1) Conduct an immediate inventory of IBM WebSphere Application Server Liberty instances to identify affected versions (17.0.0.3 through 25.0.0.8). 2) Monitor IBM security advisories closely for official patches or updates addressing CVE-2025-36124 and apply them promptly once available. 3) In the interim, review and tighten JMS messaging configurations and access controls to minimize exposure, including restricting network access to JMS endpoints and enforcing strict authentication and authorization policies. 4) Implement network-level protections such as firewall rules and intrusion detection systems to detect and block anomalous JMS traffic patterns. 5) Conduct targeted penetration testing and vulnerability assessments focusing on JMS components to identify potential exploitation attempts. 6) Establish robust monitoring and alerting for JMS service disruptions or unusual activity to enable rapid incident response. 7) Consider deploying WebSphere Liberty in isolated or segmented network zones to limit the blast radius of potential attacks. These steps go beyond generic advice by focusing on JMS-specific configurations and network segmentation tailored to this vulnerability.
Description
IBM WebSphere Application Server Liberty 17.0.0.3 through 25.0.0.8 could allow a remote attacker to bypass security restrictions caused by a failure to honor JMS messaging configuration