CVE-2026-9006: IBM WebSphere SSRF Vulnerability in Ajax Proxy
IBM WebSphere Application Server versions 8.5 and 9.0 contain a server-side request forgery (SSRF) flaw when the Ajax Proxy feature is enabled. An attacker can exploit this to make unauthorized requests from the vulnerable server, potentially accessing internal resources, bypassing security controls, or extracting sensitive information. The vulnerability requires specific network conditions but does not require user interaction or authentication.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.4 HIGH · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Weaknesses (CWE)
- CWE-918
- Affected products
- 6 configuration(s)
- Published / Modified
- 2026-06-22 / 2026-06-24
NVD description (verbatim)
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.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-9006 is an SSRF vulnerability (CWE-918) present in WebSphere Application Server 8.5 and 9.0 when the Ajax Proxy component is active. The flaw allows an unauthenticated attacker with network access to craft requests that the server will forward on their behalf to internal or external systems. Because the request originates from the trusted application server, recipient systems may grant access or disclose information they would otherwise deny to external actors. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) reflects a high-impact confidentiality and integrity risk, moderated by the additional complexity required to exploit the configuration.
Business impact
An attacker exploiting this vulnerability can perform reconnaissance against internal network infrastructure, access restricted APIs, steal credentials or sensitive data from backend systems, or trigger unauthorized actions on services the application server can reach. Organizations relying on network isolation or firewall rules to protect internal systems may find those controls circumvented. The lack of availability impact (no denial of service) means the server remains operational, potentially extending the window before discovery.
Affected systems
WebSphere Application Server 8.5 and 9.0 are vulnerable on all supported operating systems, including IBM AIX, IBM i, IBM z/OS, Linux (with Linux kernel), and Microsoft Windows. The vulnerability only manifests when the Ajax Proxy is explicitly configured and enabled. Organizations running these versions with Ajax Proxy disabled or not in use are not at risk from this specific flaw.
Exploitability
The vulnerability is network-accessible and requires no authentication or user interaction, lowering the barrier to exploitation. However, the attacker must know or discover that Ajax Proxy is enabled and must understand the internal network topology or target systems to craft effective requests. The CVSS 'H' (High) complexity reflects that successful exploitation typically requires additional reconnaissance or system knowledge rather than a simple one-click attack.
Remediation
Apply security updates from IBM for WebSphere Application Server 8.5 and 9.0 as they become available. In the interim, organizations should disable the Ajax Proxy feature if it is not actively required for business operations. Network segmentation and access controls limiting the application server's ability to reach sensitive internal systems can reduce exploitability. Review Ajax Proxy configuration logs for evidence of unauthorized requests.
Patch guidance
Check IBM's WebSphere Application Server security advisories for patched versions addressing CVE-2026-9006. Patches are typically released for supported versions; verify the specific patched version numbers in IBM's official security documentation. Test patches in a non-production environment before rollout, as WebSphere updates can affect application behavior. Prioritize systems with Ajax Proxy explicitly enabled in their configurations.
Detection guidance
Monitor network traffic from WebSphere Application Server for unexpected outbound connections to internal systems, particularly to ports associated with administrative interfaces, databases, or APIs. Enable detailed logging for Ajax Proxy requests and review logs for patterns of sequential or suspicious requests. Hunt for HTTP requests with unusual Host headers, file:// URIs, or localhost/127.0.0.1 references within application logs. Consider implementing network-based detection to flag requests originating from application server IPs to unexpected internal destinations.
Why prioritize this
CVE-2026-9006 merits immediate attention for organizations running affected WebSphere versions with Ajax Proxy enabled. The high confidentiality and integrity impact, combined with network accessibility and lack of authentication requirements, creates significant risk. Although the vulnerability is not yet in the CISA Known Exploited Vulnerabilities catalog, the straightforward nature of SSRF attacks and the widespread deployment of WebSphere mean exploitation is likely if the flaw becomes public. Organizations should treat this as a priority patch.
Risk score, explained
The CVSS 3.1 score of 7.4 (HIGH) reflects a critical combination of factors: unauthenticated network access (AV:N, PR:N) makes the attack surface large; the only mitigating complexity (AC:H) acknowledges that the attacker must overcome some environmental hurdles; the result is high impact on confidentiality and integrity (C:H, I:H), allowing information disclosure and unauthorized actions. The absence of availability impact (A:N) prevents a critical rating but does not diminish the severity for organizations defending against data theft or lateral movement.
Frequently asked questions
Is this vulnerability exploitable if Ajax Proxy is disabled?
No. The vulnerability only manifests when the Ajax Proxy feature is explicitly configured and enabled in WebSphere Application Server. If your organization does not use Ajax Proxy, this CVE does not affect you, though you should still verify your configuration to be certain.
Can this vulnerability be exploited remotely without any credentials?
Yes. The vulnerability is unauthenticated and network-accessible. An attacker does not need valid WebSphere credentials or application user accounts to attempt exploitation, though they must have network visibility to the affected server.
What internal systems are at highest risk if this is exploited?
Backend services that the application server can reach are at risk, including internal APIs, configuration management databases, authentication services, and any system relying on network isolation from untrusted clients. Systems assuming they are protected by firewall rules blocking external access may be unexpectedly exposed via the SSRF.
Should I disable Ajax Proxy immediately as a temporary control?
If Ajax Proxy is not critical to your operations, disabling it is a sound interim measure while patches are tested and deployed. If you must maintain Ajax Proxy, implement strict network access controls limiting the server's outbound connections and increase monitoring of Ajax Proxy logs.
This analysis is provided for informational purposes and should be verified against IBM's official security advisories and vulnerability data feeds. CVSS scores and patch availability are subject to change. Organizations should independently validate version numbers, affected products, and patch applicability against their deployed infrastructure before taking remediation actions. SEC.co makes no warranty regarding the completeness or accuracy of this analysis. Source: NVD (public-domain), retrieved 2026-07-29. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-10845HIGHIBM WebSphere Authentication Bypass in JAX-WS (7.3 CVSS)
- CVE-2026-8646HIGHHTTP Request Smuggling in IBM WebSphere Application Server
- CVE-2026-9071HIGHIBM WebSphere Denial of Service Vulnerability – Memory Exhaustion Attack
- CVE-2026-9320MEDIUMIBM WebSphere Denial-of-Service Vulnerability (CVSS 5.9)
- CVE-2026-45503HIGHMicrosoft Exchange Server Improper Authorization Vulnerability (CVSS 8.1)
- CVE-2026-45504HIGHMicrosoft Exchange Server SSRF Privilege Escalation Vulnerability
- CVE-2026-45501MEDIUMServer-Side Request Forgery in Microsoft Exchange Server – SSRF Risk & Patch Guidance
- CVE-2026-45502MEDIUMMicrosoft Exchange Server SSRF Information Disclosure Vulnerability