Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent-network access to WAS node
-
ExploitSend crafted request to FileTransfer servlet
-
ExecutionServlet leaks file-system path information
-
ImpactUse disclosed layout to plan follow-on attacks
Vulnerability Assessment
| Weakness |
CWE
|
| Exploitation Conditions | Exploitation requires reaching the WebSphere FileTransfer servlet, which is an administrative/node-management component of the WebSphere runtime rather than a typical application endpoint. The AV:A rating means the attacker must be on an adjacent network segment (e.g., the same admin/management LAN or Network Deployment topology), not the open Internet, which is the primary limiting factor. Vendor rates PR:N (no authentication) and UI:N (no user interaction), so no credentials or victim action are needed once adjacency is achieved; impact is confined to disclosure of file-system information (C:L) on WAS 9.0 and 8.5. |
| Impact | This is a genuinely low-priority issue despite being a network-adjacent flaw in a ubiquitous enterprise product. The vendor CVSS of 4.3 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) captures it well: impact is limited to confidentiality (C:L) with no integrity or availability effect, and the attack vector is Adjacent (AV:A), not full Internet-wide Network, which meaningfully constrains reach. The description says 'remote attacker,' which superficially conflicts with the AV:A (adjacent) rating - this is worth verifying with IBM, but AV:A is plausible because the WebSphere FileTransfer servlet is part of the Network Deployment node-synchronization/admin plumbing rather than a public-facing endpoint. No EPSS score, no CISA KEV listing, and no public exploit were provided, so there is no evidence of active exploitation - no public exploit identified at time of analysis. Signals are consistent: low technical impact (only file-system path/metadata disclosure), no automation indicator, and vendor-only reporting. Prioritize normal patching, not emergency response. |
| Exploit ScenarioDerived | An attacker positioned on the same administrative/adjacent network segment as a WebSphere deployment sends crafted requests to the FileTransfer servlet and reads back sensitive file-system information (such as absolute paths or directory structure) that aids further targeting. No public exploit code is identified, and the disclosure is confidentiality-only with no code execution or data modification. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 18, 2026
File-system information disclosure in IBM WebSphere Application Server 9.0 and 8.5 lets an attacker positioned on an adjacent network segment query the FileTransfer servlet and learn details about the server's file system, such as file and directory names or paths. Per the vendor-supplied vector (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 4.3), the flaw is rated unauthenticated and requires no user interaction, but the adjacent-network precondition means the attacker must already sit on the same management/admin LAN or WebSphere Network Deployment segment rather than reaching the service from the open Internet, and impact is limited to low-confidentiality disclosure with no integrity or availability effect. No public exploit code has been identified at time of analysis, and the CVE is not listed in CISA KEV; overall this is a low-priority issue, though it is notable because WebSphere is widely deployed in large enterprises.
RemediationAI
Apply the vendor fix; IBM has published remediation guidance for this issue at https://www.ibm.com/support/pages/node/7286610, with the patch status reported as available from the vendor (Patch available per vendor advisory). No exact fix-pack or interim-fix version number is present in the available data, so retrieve the specific WebSphere Application Server 9.0 and 8.5 fix levels and the corresponding interim fix from that IBM advisory before scheduling upgrades rather than assuming a particular release. As a compensating control pending patching, restrict network reachability to the WebSphere administrative and node-management interfaces so that only trusted administration hosts and the cell's own nodes can reach them; this is the highest-value mitigation here because the CVSS vector's AV:A rating shows the flaw is already unreachable from non-adjacent networks, but the trade-off is that legitimate remote management and wsadmin/SOAP administration from other subnets will break unless those paths are explicitly whitelisted. If the FileTransfer capability is not required in a given deployment, disable or block the FileTransfer servlet at the front-end proxy or administrative firewall so requests to it are rejected before reaching the runtime; the side effect is that any dependent file-transfer functionality used by the administration tooling will stop working, so validate management workflows before enabling this in production. Do not rely on authentication as a mitigating layer, since the vendor rates the issue PR:N (unauthenticated); hardening that path assumes no credentials are needed once adjacency is achieved. Continue to keep the administrative ports off any Internet-facing or DMZ listener, and monitor for anomalous requests to FileTransfer paths from unexpected source subnets as a detection backstop.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerable component is the FileTransfer servlet shipped with IBM WebSphere Application Server, a servlet that belongs to the administrative and node-management layer of the WebSphere runtime rather than to customer-deployed J2EE/web applications. Because it is part of the management surface, it is normally reachable only from the administrative network or from the WebSphere Network Deployment cell topology, which is exactly the constraint expressed by the AV:A (Adjacent Network) metric in the CVSS vector. The assigned root-cause class is CWE-650 (Trusting HTTP Permission Methods on the Server Side), i.e. the server mishandles or over-trusts the request method/permission semantics it receives and therefore performs file-system operations for requests it should reject or restrict; the concrete result here is information exposure (read-only, C:L) of file-system details through that servlet. The CPE record (cpe:2.3:a:ibm:websphere_application_server:*:*:*:*:*:*:*:*) is a wildcard entry and does not enumerate a granular version range, so version scoping must be taken from the IBM advisory rather than from the CPE alone. The description names WebSphere Application Server 9.0 and 8.5 as the affected releases. No additional protocol, library, or third-party dependency is implicated in the available data; the issue is confined to how the WebSphere management servlet handles incoming requests.
Know when Websphere Application Server gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Adjacent vector for an admin FileTransfer servlet (AV:A), no auth/interaction per vendor (PR:N/UI:N), and confidentiality-only path disclosure (C:L, I:N, A:N).
Primary rating from Vendor (ibm).
CVSS VectorVendor: ibm
DescriptionCVE.org
IBM WebSphere Application Server 9.0, and 8.5 could allow a remote attacker to obtain sensitive information about the file system through the FileTransfer servlet.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Websphere Application Server
View allIBM WebSphere Application Server 8.5 and 9.0 could allow a remote attacker to execute arbitrary code on the system with
IBM WebSphere Application Server (WAS) 6.1 through 6.1.0.47, 7.0 before 7.0.0.39, 8.0 before 8.0.0.11, and 8.5 before 8.
The JMX Remoting functionality in Apache Geronimo 3.x before 3.0.1, as used in IBM WebSphere Application Server (WAS) Co
Unspecified vulnerability in the IBM HTTP Server component 5.3 in IBM WebSphere Application Server (WAS) for z/OS allows
IBM WebSphere Application Server 7.0, 8.0, 8.5, and 9.0 could allow a remote attacker to traverse directories on the sys
IBM WebSphere Application Server (WAS) 7.0 before 7.0.0.43, 8.0 before 8.0.0.13, 8.5 before 8.5.5.11, 9.0 before 9.0.0.2
Unspecified vulnerability in IBM WebSphere Application Server (WAS) 6.1, 7.0 before 7.0.0.27, 8.0, and 8.5 has unknown i
Pre-authentication unsafe deserialization in IBM WebSphere Application Server 9.0 and 8.5 traditional allows remote unau
Unsafe class loading in the ORB (Object Request Broker) component of IBM WebSphere Application Server 8.5, 9.0, and Libe
Remote code execution in IBM WebSphere Application Server 8.5 and 9.0 (traditional) allows an unauthenticated network at
HTTP request smuggling in IBM WebSphere Application Server (traditional 8.5 and 9.0) and WebSphere Liberty (17.0.0.3 thr
Server-side request forgery in IBM WebSphere Application Server (traditional 9.0 and 8.5) and WebSphere Application Serv
EUVD-2026-83041
GHSA-wm4h-7wjf-j25r
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB