CVE-2026-9006 — IBM WebSphere Application Server SSRF in Ajax Proxy
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+5
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Ibm Websphere Application Server).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (ssrf), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Ibm | Websphere Application Server | ≥ 8.5.0.0 and < 8.5.5.30≥ 9.0.0.0 and < 9.0.5.29 | Vulnerable | NIST National Vulnerability Database |
| Ibm | Websphere Application Server | ≥ 9.0 and ≤ 7.0.2 Interim Fix 035≥ 8.5.0 and ≤ 7.0.3 Interim Fix 017 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.1 | CVSS 3.1 | Critical | 3.9 | 5.2 | nvd@nist.gov via NIST National Vulnerability Database |
| 7.4 | CVSS 3.1 | High | 2.2 | 5.2 | psirt@us.ibm.com via NIST National Vulnerability Database |
| 7.4 | CVSS 3.1 | High | — | — | ibm via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.39%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor outbound requests from the server to internal IPs and cloud metadata endpoints.
Analysis and videos
CVE-2026-9006: IBM WebSphere Application Server SSRF in Ajax Proxy
CVE-2026-9006 is a server-side request forgery (CWE-918) in IBM WebSphere Application Server 9.0 and 8.5 when the Ajax Proxy is configured. NVD scores it 9.1 (CVSS 3.1, Critical), while IBM's PSIRT scores it 7.4. No confirmed exploitation appears in the sources consulted, and the record lists no fixed versions, so administrators should check IBM's advisory directly.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · ibm/websphere application server
- SSVC assessment updated
- Record published
- CVSS changed · 9.1
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-105442 IBM WebSphere Application Server and WebSphere Application Server Liberty are affected by a deserialization of untrusted data 2d
- High CVE-2026-101294 IBM WebSphere Application Server and WebSphere Application Server Liberty are affected by a missing cryptographic step 2d
- High CVE-2026-95680 IBM WebSphere Application Server is affected by an authorization bypass 2d
- High CVE-2026-93907 IBM WebSphere Application Server 8.5, and 9.0 could allow a remote attacker to bypass... 2d
- High CVE-2026-103499 IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.10 and IBM WebSphere... 2d
- Critical CVE-2026-14525 Missing Authentication for Critical Function in Ibm Websphere Application Server Aug 13, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-9006 is "IBM WebSphere Application Server SSRF in Ajax Proxy", rated Critical. It affects Websphere Application Server (Ibm); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.1 describes technical severity. EPSS 0.39% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.