dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2026-9006

CRITICAL · 9.1 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 →
100/100
Remediation priority · Urgent
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 is vulnerable to server-side request forgery (SSRF) with the Ajax Proxy configured. This may allow an attacker to send unauthorized requests from the system, resulting in a security bypass or information disclosure.

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

IBM WebSphere Application Server versions 8.5 and 9.0 contain a server-side request forgery (SSRF) vulnerability in the Ajax Proxy feature. An attacker can exploit this to make the server perform unauthorized requests to internal or external resources, potentially bypassing network security controls and accessing sensitive information from internal services.

MitigationDisable or restrict the Ajax Proxy feature if not required, or implement strict allowlist-based access controls on proxy configurations. Apply IBM's official security patches for this vulnerability.

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

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
High
Integrity
High
Availability
None

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

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. Check WebSphere Application Server version
    Locate and inspect the WebSphere installation directory and verify the installed version number (typically via installation metadata, about panel, or version properties files)
    Affected if The installed version falls within 8.5.0.0 to 8.5.5.29 or 9.0.0.0 to 9.0.5.28
  2. Confirm Ajax Proxy feature is in use
    Identify whether the Ajax Proxy feature is configured or enabled in the WebSphere environment (check proxy configuration files, deployment descriptors, or administrative console settings related to Ajax Proxy)
    Affected if Ajax Proxy is actively configured or enabled in the application server configuration
  3. Review proxy configuration settings
    Examine any Ajax Proxy configuration files or settings that define request routing, destination URLs, or proxy rules
    Affected if Proxy configurations exist that allow arbitrary or insufficiently restricted destination targets
  4. Inspect network access from server
    Analyze server logs, network connections, or proxy activity records for any unauthorized or unexpected outbound requests originating from the WebSphere server
    Affected if Evidence shows the server made requests to internal resources or arbitrary external endpoints that were not explicitly intended by legitimate application logic

A user is affected if their WebSphere version is 8.5.0.0-8.5.5.29 or 9.0.0.0-9.0.5.28 AND the Ajax Proxy feature is enabled or configured in their environment.

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 or later
Fixed in 8.5.5.309.0.5.29
Interim mitigation

Disable or restrict the Ajax Proxy feature if not required, or implement strict allowlist-based access controls on proxy configurations. Apply IBM's official security patches for this vulnerability.

Recommended fix High confidence

IBM WebSphere Application Server 8.5.5.30 or later for 8.5.x; 9.0.5.29 or later for 9.0.x

  1. Back up the current WebSphere Application Server configuration, applications, and deployment manager profile
  2. Download IBM WebSphere Application Server Fix Pack 8.5.5.30 (for 8.5.x versions) or Fix Pack 9.0.5.29 (for 9.0.x versions) from IBM Fix Central (fixcentral.ihost.com)
  3. Stop all WebSphere Application Server processes including the deployment manager and node agents
  4. Install the downloaded fix pack using the IBM Installation Manager or Update Installer following IBM's standard fix pack installation procedures
  5. Verify the fix pack installation completed successfully by checking the version via aboutVersion command or admin console
  6. Start the deployment manager, sync nodes, and start node agents
  7. Validate that the Ajax Proxy configuration is functioning correctly and the SSRF vulnerability is remediated
  8. Restart all WebSphere Application Server instances
Caveat Review IBM WebSphere Migration Guide for potential compatibility impacts; test applications in non-production environment before deploying upgrade to production

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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