Oracle Helidon EUVD-2026-62129

The vulnerability requires that the target is running Oracle Helidon version 3.2.18 specifically with the Imperative Web Server component active - deployments using only the Reactive Web Server are not confirmed affected. The attack requires HTTP network access to the server; no authentication, no user interaction, and no elevated complexity is needed, meaning standard deployments of this exact version without additional perimeter controls are vulnerable. Exploitation is limited by: (1) the specific version pin to 3.2.18 - operators on earlier or later Helidon versions are not confirmed affected by this CVE; (2) network reachability to the HTTP port hosting the Imperative Web Server - internal-only deployments isolated from untrusted networks face substantially reduced exposure; (3) the impact ceiling is partial data read and partial data write/delete only - no full system compromise, code execution, or service disruption is indicated. No non-default configuration, special feature flag, or particular deployment mode beyond running Helidon 3.2.18's Imperative Web Server is required to be vulnerable based on the available description.

The CVSS 3.1 score of 7.2 (High) is driven by the scope change (S:C) combined with a fully unauthenticated, network-accessible, low-complexity attack vector (AV:N/AC:L/PR:N/UI:N). Per-system impact is moderate - C:L and I:L with A:N - meaning no single-system full compromise or denial of service, but the S:C escalation is meaningful in multi-service environments. No EPSS data was available in the input, so exploitation probability cannot be quantified independently. There is no CISA KEV listing and no public POC identified, placing this in the pre-exploitation disclosure category and reducing immediate incident response urgency relative to actively weaponized CVEs. Oracle's use of the phrase 'easily exploitable' is Oracle-standard language for the AV:N/AC:L/PR:N attack profile, confirming a low technical barrier, not a novel or out-of-band finding. The primary risk driver for prioritization is deployment topology: Helidon instances directly reachable from untrusted networks with no compensating authentication proxy are at meaningful risk; internally isolated deployments face substantially lower exposure. The absence of availability impact (A:N) and the partial data impact bounds limit the blast radius compared to full RCE scenarios.

An unauthenticated attacker with HTTP access to the Helidon 3.2.18 Imperative Web Server sends a specially crafted HTTP request that bypasses authentication enforcement, directly reaching protected API routes without valid credentials. The attacker reads a subset of accessible application data - such as user records or configuration artifacts - and issues unauthorized write operations to modify or insert data within the server's data scope. If the Helidon instance serves as a gateway to backend microservices, the scope change means the attacker may further pivot into those downstream systems through the compromised front-door endpoint.