Oracle Helidon EUVD-2026-105992

Exploitation requires that the Helidon application use the helidon-webclient-websocket component and process attacker-reachable HTTP/WebSocket traffic; per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no authentication or user interaction is needed. The key limiting factor is scope of impact rather than preconditions: successful attacks yield only partial read access to a subset of Helidon-accessible data and a partial denial of service, not full data exposure, data modification, or complete outage. Affected deployments are limited to Helidon versions 4.0.0-4.5.5 and 27.0.0; versions outside these ranges are not in scope. Because the vulnerable code is the outbound WebClient/WebSocket layer, real-world exploitability may further depend on whether the Helidon service initiates connections to endpoints an attacker can influence - confirm this nuance against Oracle CPU October 2026.

This is a moderate-severity issue that should be patched on a normal cycle rather than treated as an emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L, base 6.5) indicates a genuinely remote, low-complexity, unauthenticated vector with no user interaction, which raises its baseline concern. However, the impacts are deliberately limited: only partial confidentiality (C:L - read access to a subset of data), no integrity impact (I:N), and only partial availability loss (A:L - partial DOS), so this is not a full-compromise or RCE bug despite being network-reachable. No EPSS score was supplied in the input, the CVE is NOT listed in CISA KEV, and no public proof-of-concept is referenced - so there is no public exploit identified at time of analysis and no evidence of active exploitation. The affected component (helidon-webclient-websocket) is the outbound WebClient/WebSocket layer, which suggests exploitation may depend on the Helidon client connecting to an attacker-influenced endpoint rather than a purely inbound server-side attack; the description's generic 'network access via HTTP' phrasing does not clarify this, so verify the precise attack direction with Oracle's advisory. Net assessment: real but not urgent - a medium priority driven by easy exploitability but capped by partial, read-only/DOS impact.

A remote, unauthenticated attacker sends crafted HTTP/WebSocket traffic that is processed by the Helidon WebClient WebSocket component, causing it to disclose a subset of accessible data and/or enter a degraded state that partially disrupts the service. Because the component is the WebClient (outbound), the realistic trigger is likely a malicious or attacker-controlled server/endpoint that the Helidon application connects to. No public proof-of-concept is referenced in the available data.