dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2026-9320

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

IBM WebSphere Application Server (traditional 8.5, 9.0) and Liberty (17.0.0.3 through 26.0.0.6) contain a denial of service vulnerability where a remote attacker can send specially-crafted requests causing excessive memory consumption on the server.

MitigationApply IBM security patches for this vulnerability when released; implement request rate limiting and memory consumption monitoring as interim controls.

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 WebSphere product type and version
    For traditional WebSphere, run 'versionInfo.sh' (Linux/AIX) or 'versionInfo.bat' (Windows) from the install_root/bin directory. For Liberty, check the version in the server.xml file or run 'server version' from the Liberty bin directory.
    Affected if The installed version falls within the affected ranges: traditional 8.5.0.0-8.5.5.29, 9.0.0.0-9.0.5.28, or Liberty 17.0.0.3-26.0.0.6
  2. Verify traditional WebSphere fix pack level
    Locate the installation root directory and check the product version in the /properties/version directory or via the administrative console under 'Server > Server1 > Version' information.
    Affected if The fix pack is below 8.5.5.30 for 8.5.x versions or below 9.0.5.29 for 9.0.x versions
  3. Verify Liberty version
    Check the liberty version by running 'java -jar wlp-*.jar --version' or 'server version --verbose' against the running server. Also inspect the server.xml for version information in the <server> element.
    Affected if The Liberty version is 17.0.0.3 through 26.0.0.6 inclusive
  4. Confirm server is network exposed
    Review network configuration to determine if the WebSphere HTTP port (default 9080 for traditional, 9080 for Liberty) is accessible from external networks or untrusted zones.
    Affected if The HTTP listener is exposed to remote attackers (not localhost-only or behind a protected network)

You are affected if your WebSphere traditional version is 8.5.0.0-8.5.5.29 or 9.0.0.0-9.0.5.28, or Liberty version is 17.0.0.3-26.0.0.6, and the server HTTP port is network-accessible.

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 security patches for this vulnerability when released; implement request rate limiting and memory consumption monitoring as interim controls.

Recommended fix High confidence

WebSphere Application Server 8.5.5.30+ / 9.0.5.29+ / Liberty 26.0.0.7+

  1. 1. Determine your current WebSphere Application Server version by checking the installation directory or using the versionInfo command
  2. 2. Identify the appropriate fix pack for your release: For 8.5.x, upgrade to 8.5.5.30 or later; For 9.0.x, upgrade to 9.0.5.29 or later; For Liberty 17.0.0.3 through 26.0.0.6, upgrade to 26.0.0.7 or later
  3. 3. Download the corresponding fix pack from IBM Fix Central (https://www.ibm.com/support/fixcentral) or through your IBM Support account
  4. 4. Schedule a maintenance window and back up your current WebSphere installation and configuration
  5. 5. Apply the fix pack following IBM's installation instructions (using Installation Manager or the update installer)
  6. 6. Restart the WebSphere Application Server services
  7. 7. Verify the server starts successfully and the version now reflects the patched release
Caveat IBM fix packs are generally backward compatible, but always test in a non-production environment first as custom configurations or applications may behave differently after the upgrade

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9320 — 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-9320 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