dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2026-4410

HIGH · 7.5 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to after 26.0.0.5 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 - Liberty 19.0.0.7 through 26.0.0.5 and IBM WebSphere Application Server 9.0, and 8.5 and WebSphere Application Server Liberty 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 · high confidence

A denial of service vulnerability in IBM WebSphere Application Server (traditional and Liberty versions 19.0.0.7 through 26.0.0.5, 9.0, and 8.5) allows remote attackers to exhaust server memory resources by sending specially-crafted requests.

MitigationApply IBM security patches or upgrade to a non-vulnerable version; implement request rate limiting and monitoring as a compensating control until patching is complete.

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.29>= 9.0.0.0, <= 9.0.5.27>= 19.0.0.7, <= 26.0.0.5

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 installation type
    Determine if you are running WebSphere Application Server Traditional or Liberty by checking the installation directory structure and startup scripts (look for 'wlp' directory for Liberty, or 'profiles' directory for Traditional)
    Affected if The installation is either Traditional or Liberty variant of IBM WebSphere Application Server
  2. Locate and retrieve the WebSphere version
    For Traditional: Navigate to the install_root/bin and run 'versionInfo.sh' (Linux/Unix) or 'versionInfo.bat' (Windows). For Liberty: Check the 'wlp/lib/versions' directory or run 'bin/productInfo version'
    Affected if The version command output cannot be retrieved (indicating WebSphere may not be installed)
  3. Compare installed version against affected ranges
    Review the version output and compare the full version number (e.g., 9.0.5.27) against the vulnerable ranges: 8.5.0.0-8.5.5.29, 9.0.0.0-9.0.5.27, and 19.0.0.7-26.0.0.5
    Affected if The installed version falls within any of the listed vulnerable version ranges
  4. Verify if WebSphere HTTP ports are exposed
    Check network listener configuration in the WebSphere admin console or by reviewing server.xml (Liberty) or server-index.xml (Traditional) for enabled ports, typically 9080 (HTTP) or 9443 (HTTPS)
    Affected if WebSphere HTTP/HTTPS listeners are bound to accessible network interfaces and accepting external requests
  5. Confirm the server process is running
    Check for running Java processes with WebSphere classpath or use system commands: 'ps -ef | grep WebSphere' (Linux/Unix) or check Windows services for 'IBM WebSphere Application Server'
    Affected if The WebSphere server process is actively running and accepting requests

You are affected if WebSphere Application Server (Traditional or Liberty) is installed and running with a version number that falls within 8.5.0.0-8.5.5.29, 9.0.0.0-9.0.5.27, or 19.0.0.7-26.0.0.5, and the HTTP ports are exposed to network attackers.

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 a release after 26.0.0.5
Interim mitigation

Apply IBM security patches or upgrade to a non-vulnerable version; implement request rate limiting and monitoring as a compensating control until patching is complete.

Recommended fix Moderate confidence

WebSphere Application Server Liberty 26.0.0.6+ or WebSphere Application Server 9.0.5.28+ / 8.5.5.30+

  1. 1. Identify your current IBM WebSphere Application Server version using the wsadmin tool or administration console
  2. 2. For WebSphere Application Server Liberty: Upgrade to version 26.0.0.6 or later
  3. 3. For WebSphere Application Server traditional: Upgrade to version 9.0.5.28 or later for the 9.0.x line
  4. 4. For WebSphere Application Server traditional: Upgrade to version 8.5.5.30 or later for the 8.5.x line
  5. 5. After upgrade, restart the application server to ensure the fix is applied
  6. 6. Monitor server memory usage after applying the fix to verify the vulnerability is resolved
Caveat Upgrade to a new minor version may require compatibility testing with existing applications; review IBM's migration guide for behavioral changes

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

Fix this in Websphere Application Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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