What is the CVSS score of CVE-2026-9006?

CVE-2026-9006 has a CVSS 3.1 base score of 9.1 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.2%.

Which versions of IBM WebSphere Application Server are affected by CVE-2026-9006?

IBM WebSphere Application Server versions 8.5 and 9.0 contain an unauthenticated server-side request forgery vulnerability allowing attackers to manipulate server requests and access internal systems…. A patch is available.

How to fix or mitigate CVE-2026-9006?

Within 24 hours: Identify all WebSphere 8.5/9.0 deployments with Ajax Proxy enabled; disable the proxy where operationally feasible. Within 7 days: Apply IBM vendor patches for WebSphere Application Server 8.5 and 9.0 across all production systems. Within 30 days: Execute vulnerability rescans to confirm patch application and validate that no unpatched instances remain.

IBM WebSphere Application Server CVE-2026-9006

EUVD-2026-38252 CRITICAL

Server-Side Request Forgery (SSRF) (CWE-918)

2026-06-22 ibm

GHSA-57wv-8v6f-4353

Information Disclosure SSRF IBM Websphere Application Server

9.1

CVSS 3.1 · NVD

Severity by source

Vendor (ibm) PRIMARY

HIGH

qualitative

NVD

9.1 CRITICAL

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

vuln.today AI

8.2 HIGH

Network-reachable proxy, no auth or UI needed; high confidentiality via SSRF reads, but integrity impact via forged requests is realistically low, not high.

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

4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Updated

Jun 23, 2026 - 20:58 vuln.today

v3 (cvss_changed)

Analysis Updated

Jun 23, 2026 - 20:58 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Jun 23, 2026 - 20:52 vuln.today

cvss_changed

Severity Changed

Jun 23, 2026 - 20:52 NVD

HIGH CRITICAL

CVSS changed

Jun 23, 2026 - 20:52 NVD

7.4 (HIGH) 9.1 (CRITICAL)

Analysis Generated

Jun 22, 2026 - 16:03 vuln.today

DescriptionNVD

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.

AnalysisAI

Server-side request forgery in IBM WebSphere Application Server 8.5 and 9.0 allows remote unauthenticated attackers to coerce the server into issuing arbitrary outbound requests when the Ajax Proxy is configured, enabling security bypass and information disclosure. IBM has released fixes and no public exploit is identified at time of analysis; EPSS is low (0.23%, 14th percentile) and SSVC marks exploitation as 'none' despite a CVSS of 9.1.

Technical ContextAI

WebSphere Application Server is IBM's flagship Java EE/Jakarta EE runtime used to host enterprise web and SOA workloads. The flaw lives in the optional Ajax Proxy component (a server-side HTTP forwarder bundled with the Dojo/AJAX support to relay XHR calls and bypass browser same-origin restrictions), which fails to adequately validate or restrict destination URLs supplied by clients. This is a classic CWE-918 Server-Side Request Forgery: the trusted server makes outbound requests on behalf of an attacker, potentially reaching internal services, cloud metadata endpoints, or otherwise unreachable hosts. Affected CPE is cpe:2.3:a:ibm:websphere_application_server across 8.5 and 9.0 branches.

RemediationAI

Vendor-released patch: apply the Interim Fixes referenced in IBM advisory https://www.ibm.com/support/pages/node/7276600 - Interim Fix 017 for the 8.5 stream and Interim Fix 035 for the 9.0 stream - or upgrade to a Fix Pack that supersedes them. If patching must be deferred, disable the Ajax Proxy by removing or commenting out the proxy servlet mapping and proxy-config.xml entries in affected web applications, which eliminates the SSRF vector at the cost of breaking any client-side code that relies on cross-domain XHR proxying. Additionally, restrict egress from WAS hosts at the network layer (deny outbound traffic to cloud metadata IPs such as 169.254.169.254, internal management subnets, and arbitrary internet destinations), accepting that this may block legitimate outbound integrations and require an allow-list. Place a reverse proxy or WAF in front of WAS to filter requests targeting known Ajax Proxy URL paths until the fix is deployed.