Skip to main content
VulnerabilityPublished Updated

CVE-2025-36047: IBM WebSphere Application Server Liberty · Unthrottled Resource Allocation

Affects IBM WebSphere Application Server LibertySource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% 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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBM WebSphere Application Server LibertyAffected
  • =18.0.0.2
Fixed in–

AI-suggested

  1. Apply official patches or updates from IBM as soon as they become available for affected WebSphere Liberty versions.
  2. Implement network-level protections such as Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) to detect and block anomalous or malformed requests that could trigger excessive memory consumption.
  3. Configure rate limiting and throttling on incoming requests to prevent resource exhaustion from high request volumes or malicious payloads.
  4. Monitor server memory usage and application performance metrics closely to detect early signs of resource exhaustion or abnormal behavior.
  5. Consider deploying WebSphere Liberty instances behind load balancers that can isolate and mitigate the impact of DoS attempts.
  6. Conduct regular security assessments and penetration testing to identify and address resource allocation weaknesses.
  7. Review and harden application-level input validation to reduce the risk of malformed requests causing resource spikes.
  8. Maintain an incident response plan specifically addressing denial of service scenarios to ensure rapid recovery.

Description

IBM WebSphere Application Server Liberty 18.0.0.2 through 25.0.0.8 is vulnerable to a denial of service, caused by sending a specially-crafted request. A remote attacker could exploit this vulnerability to cause the server to consume memory resources.

References

Community reviews

Loading reviews…