Oracle Helidon EUVD-2026-105985

Exploitation targets the helidon-cors cross-origin resource sharing component in Helidon 4.0.0 through 4.5.5 and requires a Helidon application that actually exposes CORS-enabled endpoints. Per CVSS PR:N the attacker needs no credentials, but UI:R means success depends on interaction from a human victim other than the attacker (e.g. an active user visiting an attacker-controlled page whose browser issues the cross-origin request). AC:H indicates additional conditions beyond the attacker's control must align, so exploitation is not reliable. Impact is limited to low integrity (some unauthorized update/insert/delete) with no confidentiality or availability effect, which caps realistic damage. Deployments not using helidon-cors, or not on an affected 4.x version, are not exposed.

This is a genuinely low-priority issue, and the signals are consistent rather than conflicting. Oracle's CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N, base 3.1) describes a network-reachable but hard-to-exploit flaw: high attack complexity (AC:H), mandatory interaction from a victim other than the attacker (UI:R), and only a low integrity impact with no confidentiality or availability loss. No EPSS score was supplied in the input, so exploitation probability cannot be quantified. The CVE is not in CISA KEV and no POC is referenced, so this is no public exploit identified at time of analysis - there is no evidence of active exploitation or weaponization. The combination of AC:H plus UI:R plus a Low-only integrity impact means that even if exploited, attacker benefit is marginal. The one discordant signal is the 'Authentication Bypass' tag, which is not supported by the description (a helidon-cors integrity flaw requiring victim interaction is a cross-origin/CORS enforcement weakness, not an authentication bypass) - treat that tag as unreliable. Net: a low-CVSS, low-real-risk issue appropriate for routine patching, not emergency response.

An attacker hosts a malicious web page and lures an authenticated Helidon user into visiting it; a weakness in helidon-cors cross-origin handling lets a crafted cross-origin request reach the application and perform a limited unauthorized write, insert, or delete against some Helidon-accessible data. The high attack complexity and the requirement that a separate human victim interact make reliable exploitation difficult. No public proof-of-concept is referenced in the available data.