HIGH 7.5

CVE-2026-9071: IBM WebSphere Denial of Service Vulnerability – Memory Exhaustion Attack

IBM WebSphere Application Server versions 9.0, 8.5, and Liberty versions 17.0.0.3 through 26.0.0.6 contain a vulnerability that allows remote attackers to crash or severely degrade server performance by sending specially crafted requests. The vulnerability causes the affected server to consume excessive memory, leading to denial of service. No authentication is required to exploit this issue, and attackers can trigger it over the network.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses (CWE)
CWE-400
Affected products
8 configuration(s)
Published / Modified
2026-06-22 / 2026-06-23

NVD description (verbatim)

IBM WebSphere Application Server 9.0, and 8.5 and IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.6 are 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.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-9071 is a memory exhaustion denial-of-service vulnerability in IBM WebSphere Application Server and WebSphere Liberty. The flaw is classified under CWE-400 (Uncontrolled Resource Consumption) and is triggered when the server processes a maliciously formatted request. The vulnerability affects both traditional WebSphere Application Server (versions 8.5 and 9.0) and the lighter-weight Liberty profile (17.0.0.3 through 26.0.0.6). The attack vector is network-based, requires no privileges, and cannot be mitigated by user interaction, making it immediately exploitable by any remote actor.

Business impact

Organizations running affected WebSphere deployments face immediate availability risk. A successful attack will consume server memory until the application becomes unresponsive, disrupting business-critical applications hosted on those servers. Recovery typically requires manual intervention and server restart, extending downtime. In multi-tier environments, the impact may cascade to dependent systems. Industries relying on WebSphere for transaction processing, enterprise applications, or integration middleware face particular risk of revenue loss and SLA violations.

Affected systems

The vulnerability affects IBM WebSphere Application Server 8.5 and 9.0, as well as IBM WebSphere Application Server - Liberty from version 17.0.0.3 through 26.0.0.6. These components run on multiple operating systems including Windows, Linux, macOS, AIX, IBM i, and z/OS. Organizations should inventory all WebSphere deployments across their infrastructure to identify affected instances, including both production and non-production environments that may be exposed to untrusted network traffic.

Exploitability

This vulnerability presents high exploitability risk. The attack requires no authentication, no user interaction, and can be launched over the network by any remote actor with network connectivity to the affected server. The low attack complexity means that a standard HTTP request or similarly crafted network packet can trigger the condition. Given the ease of exploitation, defenders should assume active reconnaissance and attack attempts are likely once the vulnerability becomes widely known.

Remediation

Immediate action is required for organizations running affected WebSphere versions. Contact IBM for availability of patches, verify against the vendor advisory for your specific version and platform combination, and apply patches to the earliest affected versions in your environment. In the interim, network segmentation to restrict access to WebSphere servers to trusted clients only is recommended. Monitor deployed instances for unusual memory consumption patterns that may indicate exploitation attempts.

Patch guidance

Organizations should verify patch availability directly through IBM's support portal and security bulletins, as patch version numbers vary by platform and WebSphere variant. Prioritize patching of externally-facing or internet-connected WebSphere instances first. Test patches in non-production environments before production deployment. Liberty deployments may have different patch cycles than traditional WebSphere Application Server, so check version-specific guidance from IBM. Establish a maintenance window for patching given the denial-of-service nature of the vulnerability.

Detection guidance

Monitor WebSphere server memory utilization for unexplained spikes correlated with unusual request patterns. Enable access logging and review for requests with abnormal characteristics preceding memory exhaustion events. Configure alerting on sustained high memory consumption. Collect and analyze network traffic to the affected servers for malformed or suspicious request signatures. WebSphere diagnostic logs may record resource consumption warnings before full failure; ensure these logs are actively monitored and retained for forensic analysis.

Why prioritize this

This vulnerability merits immediate prioritization due to the combination of high CVSS score (7.5), complete lack of authentication requirements, network-based attack vector, and direct impact to application availability. The denial-of-service nature means that even a single successful exploitation event will disrupt business operations. The broad range of affected Liberty versions increases the likelihood that many organizations run vulnerable instances without realizing it.

Risk score, explained

The CVSS 3.1 score of 7.5 (HIGH) reflects a network-accessible vulnerability with no authentication or user interaction required. However, the scope is unchanged (attacks do not breach isolation), and there is no confidentiality or integrity impact—only availability is affected. The score appropriately reflects that while the attack is trivial to execute, the blast radius is contained to the targeted server's availability rather than representing a system-wide compromise or data breach vector.

Frequently asked questions

Do I need to update if I'm running WebSphere Application Server 7.0 or earlier?

No, this vulnerability only affects WebSphere Application Server 8.5, 9.0, and WebSphere Liberty 17.0.0.3 through 26.0.0.6. Earlier versions are not listed as affected. However, you should verify your exact version by checking the version string in your administration console or logs, as version identification errors are common during patching efforts.

Can this vulnerability be exploited from inside my network only, or does it require internet access?

The vulnerability can be exploited by any remote attacker with network connectivity to the affected WebSphere server. This includes attackers from the internet if the server is externally accessible, as well as from insider threats or compromised machines on your internal network. Network segmentation and firewall rules restricting access to WebSphere administration and application ports are critical mitigations.

What is the difference between this affecting WebSphere Application Server versus WebSphere Liberty?

WebSphere Liberty is a lightweight, cloud-optimized variant of WebSphere designed for containerized and microservices deployments. Both products share core components but have different version numbering and patch schedules. If you run Liberty in containers or modern application platforms, check your container image tags against the affected Liberty versions (17.0.0.3 through 26.0.0.6) even if you don't run traditional WebSphere Application Server.

If I cannot patch immediately, what can I do to reduce my risk?

Implement network access controls to restrict which clients can reach your WebSphere servers. Use firewall rules, WAF policies, or load balancer filtering to limit traffic to known-good sources. Monitor memory consumption and set aggressive alerts for unexplained utilization spikes. Implement connection rate limiting if your infrastructure supports it. These measures reduce—but do not eliminate—the risk, so patching should remain your primary objective.

This analysis is provided for informational purposes. The information herein is derived from public vulnerability disclosures and IBM's official guidance. Patch version numbers and availability must be verified against IBM's official security bulletins and support portal before deployment. Organizations should conduct their own risk assessment based on their specific infrastructure, network exposure, and business criticality. This content does not constitute formal security advice or replace consultation with qualified security professionals for your environment. Source: NVD (public-domain), retrieved 2026-07-29. Analysis generated by SEC.co (claude-haiku-4-5).