Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain man-in-the-middle network position
-
DeliveryIntercept admin client TLS session
-
ExploitExploit improper certificate validation (CWE-295)
-
ExecutionRelay/decrypt administrative traffic
-
ImpactHarvest sensitive information
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V12 - Secure Communication Certificate validation
|
| Exploitation Conditions | Exploitation requires the attacker to hold an active man-in-the-middle position on the network path used by the WebSphere Application Server Liberty administrative client (affected versions 17.0.0.3 through 26.0.0.9) - for example a shared LAN segment, hostile Wi-Fi, compromised gateway/proxy, or an internal lateral foothold. The underlying defect is improper TLS certificate validation (CWE-295) in the administrative client, so the condition is that the client initiates a TLS connection the attacker can intercept and present a fraudulent certificate to. Limiting factors: this is reflected in the HIGH attack complexity (AC:H) - an attacker on the open internet with no interception capability cannot exploit it; network segmentation of administrative traffic, mutual TLS enforcement, or trusted-path administration substantially reduces exposure. No authentication is required (PR:N) and no user interaction is needed (UI:N). |
| Impact | This is a moderate-severity information-disclosure flaw (CVSS 6.5) rather than a top-tier priority. The IBM-provided CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N) tells a consistent story for a CWE-295 improper-certificate-validation issue: the attack is network-based and needs no privileges or user interaction, but carries HIGH attack complexity (AC:H) because the attacker must first achieve a man-in-the-middle position on the network path between the WebSphere Liberty administrative client and its endpoint - a precondition that is not trivially met from the open internet. Confidentiality impact is HIGH (sensitive data exposed) with only LOW integrity impact and no availability impact. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The practical risk is therefore gated almost entirely by whether an attacker can position themselves on the relevant network segment (e.g., shared LAN, compromised router, hostile Wi-Fi, or internal lateral position). In a hardened, segmented administrative network the real-world risk is low-to-moderate despite the HIGH confidentiality rating; on a flat or untrusted network it is more meaningful. No key signals are directly conflicting, but note the absence of EPSS/KEV/POC data means exploitation likelihood cannot be quantified from the input. |
| Exploit ScenarioDerived | An attacker who can intercept traffic between a WebSphere Application Server Liberty administrative client and its target (for example on a shared or compromised network segment) exploits improper TLS certificate validation to transparently proxy the connection. Because the client fails to properly verify the server certificate, the attacker decrypts or relays the administrative session and harvests sensitive information such as credentials or configuration data. No public exploit code was identified in the input, and the HIGH attack complexity reflects the need to first obtain the man-in-the-middle position. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Man-in-the-middle interception of traffic from the IBM WebSphere Application Server - Liberty administrative client (versions 17.0.0.3 through 26.0.0.9) can expose sensitive information, because the client does not properly validate TLS certificates (CWE-295). The flaw is rated CVSS 6.5 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N): no authentication or user interaction is required, but exploitation demands that an attacker already occupy a position on the network path - a shared LAN segment, hostile Wi-Fi, compromised gateway or proxy, or an internal lateral foothold - making it a moderate-severity information-disclosure issue rather than a top-tier priority. There is no public exploit identified at time of analysis and the issue is not reported as confirmed actively exploited (CISA KEV); internet-only attackers with no interception capability cannot trigger it.
RemediationAI
No vendor-released patch version is specified in the available intelligence, so treat IBM's advisory at https://www.ibm.com/support/pages/node/7291394 as the authoritative source and apply the Liberty fix pack or interim fix level it names as soon as it is published; upgrading past the affected range (17.0.0.3 through 26.0.0.9) is the definitive fix. Until then, compensate for the missing certificate validation by removing the attacker's required position rather than relying on generic hardening: restrict administrative client traffic to a dedicated, segmented management VLAN or trusted-path network so no untrusted host can sit on the path, and route administration through a hardened jump host or VPN with mutual TLS enforced end to end - the trade-off is reduced administrative flexibility and additional credential/PKI management. Where the client or its fronting proxy can be configured to require server certificate verification or pinning, enable it and distribute the expected certificate or CA explicitly; the cost is certificate lifecycle overhead and possible breakage on rotation. Blocking administrative management ports from user and guest networks and monitoring for unexpected TLS interception or certificate changes on those paths adds detection value, though it will not fix the underlying client defect and may generate false positives on legitimate proxy inspection. Because exploitation requires an on-path attacker, prioritizing network segmentation and trusted-path administration reduces exposure even before a patch is available.
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 root cause class is CWE-295, improper certificate validation, in the TLS client component used by the WebSphere Application Server - Liberty administrative client. Instead of anchoring trust to a known CA or pinned certificate, the client accepts a certificate presented by a party it did not authenticate, so any adversary who can transparently relay or terminate the TLS session can read administrative traffic and, to a lesser degree, influence it (reflected in the C:H/I:L impact pair). Because the attack vector is network (AV:N) with no privileges (PR:N) and no user action (UI:N), the only real gate is the attacker's position on the path; that prerequisite is captured by the HIGH attack complexity (AC:H) and by the unchanged scope (S:U) - the compromise does not cross a security boundary, it leaks data from the client session. Administrative management traffic in Liberty deployments often traverses internal networks, jump hosts, and shared management VLANs, which is exactly where this defect is reachable. Affected artifacts per the EUVD record are WebSphere Application Server - Liberty 17.0.0.3 up to and including 26.0.0.9 (EUVD-2026-100488), tracked under CVE-2026-77816 and reported by IBM PSIRT.
Know when the next one hits your stack
- 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:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
MITM via improper cert validation is network-reachable but requires attacker interception positioning (AC:H) and no auth (PR:N); high confidentiality exposure, low integrity tampering, no availability impact.
Primary rating from Vendor (us).
CVSS VectorVendor: us
DescriptionCVE.org
IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.9 administrative client could allow man-in-the-middle attacks. An attacker could exploit this vulnerability to obtain sensitive information.
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.
EUVD-2026-100488
GHSA-6v8r-r3rp-wwmm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB