Summary
CVE-2026-73905 is a critical, unauthenticated remote compromise vulnerability in the Imperative Web Server component of Oracle Helidon, part of Oracle Fusion Middleware. Oracle describes it as an "easily exploitable" flaw that lets an unauthenticated attacker with network access via HTTP fully compromise and take over a vulnerable Helidon instance. The issue carries a maximum-severity CVSS v3.1 base score of 9.8 and was disclosed as part of Oracle’s August 2026 Critical Patch Update.
Technical details
- Root cause: Oracle’s advisory does not disclose the specific coding flaw (e.g., no CWE identifier or technical root-cause detail has been published); the affected component is identified only as Helidon’s "Imperative Web Server."
- Trigger conditions: Oracle characterizes the vulnerability as "easily exploitable," requiring no special access conditions or complex setup to trigger.
- Attack vector: Network-based, delivered over HTTP, requiring no authentication (PR:N) and no user interaction (UI:N), with low attack complexity (AC:L).
- Impact: Successful exploitation results in "takeover of Helidon," with high impact to confidentiality, integrity, and availability (C:H/I:H/A:H) and no change in scope (S:U) per Oracle’s own CVSS rating.
- No public proof-of-concept, exploit code, or independent technical writeup has been identified at this time; Oracle’s advisory is currently the sole authoritative source of information.
Affected software
- Oracle Helidon (Oracle Fusion Middleware), Imperative Web Server component
- Version 4.5.0 (the only version listed by Oracle as affected in the CVE record)
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Apply the patch provided in Oracle’s August 2026 Critical Patch Update (CSPU) for Helidon. Organizations running Helidon 4.5.0 should upgrade to the version specified as fixed in Oracle’s advisory as soon as possible, following standard Oracle CPU patch-application procedures.
- If immediate patching is not possible: Restrict network exposure of Helidon-based web services to trusted networks only, and place internet-facing Helidon instances behind a web application firewall or reverse proxy that can restrict/monitor inbound HTTP traffic until the patch can be applied.
- Review Oracle’s Critical Patch Update advisory directly for the exact patched release number and any Oracle-recommended workarounds, as Oracle’s public record for this CVE does not itself list a fixed version number.
- Monitor Helidon-based application logs for anomalous or unauthenticated HTTP requests as a precaution while remediation is in progress.

