dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2026-9071

HIGH · 7.5 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to 8.5.5.30 / 9.0.5.29 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a memory exhaustion denial of service vulnerability in IBM WebSphere Application Server (traditional 8.5, 9.0) and WebSphere Liberty (17.0.0.3 through 26.0.0.6). A remote attacker can send specially-crafted HTTP requests that cause excessive memory consumption, potentially leading to service unavailability.

MitigationApply IBM's security patches for this vulnerability. Implement request rate limiting and monitoring for abnormal memory consumption patterns as a compensating control until patches can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Websphere Application ServerApplication
Affected:>= 8.5.0.0, < 8.5.5.30>= 9.0.0.0, < 9.0.5.29>= 17.0.0.3, < 26.0.0.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the WebSphere product type
    Determine if you are running IBM WebSphere Application Server traditional or WebSphere Liberty. Check the installation directory: traditional typically under IBM/WebSphere/AppServer, Liberty under wlp/ or similar.
    Affected if Running either traditional WebSphere or Liberty without knowing which
  2. Check the installed WebSphere version
    For traditional: look in AboutWebSphere Application Server version details or run 'versionInfo -version' command. For Liberty: check the version in the usr/servers/<serverName>/logs/message.log or run 'bin/server version <serverName>'. Compare the version number to the affected ranges: traditional 8.5.0.0 to 8.5.5.29, 9.0.0.0 to 9.0.5.28; Liberty 17.0.0.3 to 26.0.0.6.
    Affected if Installed version falls within 8.5.0.0-8.5.5.29, 9.0.0.0-9.0.5.28 (traditional), or 17.0.0.3-26.0.0.6 (Liberty)
  3. Confirm HTTP endpoints are exposed
    Review server.xml (Liberty) or http.xml/plugin-cfg.xml (traditional) to verify HTTP channels or web containers are enabled and accessible from the network.
    Affected if HTTP or web container is enabled and reachable from external or untrusted networks
  4. Verify memory monitoring is in place
    Check if WebSphere health monitoring, IBM Tivoli, or external monitoring tools are configured to alert on abnormal JVM heap memory usage.
    Affected if No memory consumption alerts are configured, leaving memory exhaustion undetected

You are affected if you run WebSphere traditional 8.5.x below 8.5.5.30 or 9.0.x below 9.0.5.29, or Liberty 17.0.0.3 through 26.0.0.6, with HTTP endpoints exposed and no memory monitoring to detect the exhaustion pattern.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.5.5.30 / 9.0.5.29 / 26.0.0.7 or later
Fixed in 8.5.5.309.0.5.2926.0.0.7
Interim mitigation

Apply IBM's security patches for this vulnerability. Implement request rate limiting and monitoring for abnormal memory consumption patterns as a compensating control until patches can be applied.

Recommended fix High confidence

WebSphere Application Server 8.5.5.30, 9.0.5.29, or Liberty 26.0.0.7 (depending on your product line)

  1. For WebSphere Application Server 8.5.x: Upgrade to version 8.5.5.30 or later
  2. For WebSphere Application Server 9.0.x: Upgrade to version 9.0.5.29 or later
  3. For WebSphere Application Server Liberty: Upgrade to version 26.0.0.7 or later
  4. After upgrading, restart the WebSphere Application Server to apply the changes
  5. Verify the server starts successfully and monitor for normal memory consumption
Caveat Standard version upgrade; review IBM's migration guide for any compatibility considerations specific to your application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Websphere Application Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9071 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9071 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data