Oracle Helidon is part of Oracle Fusion Middleware used across enterprises; an unauthenticated network flaw allows full data compromise—likely high-impact for many organizations.
CVE-2026-73916
Unauthenticated HTTP access allows full data compromise in Oracle Helidon 3.2.18
Is CVE-2026-73916 being exploited?
Not confirmed. CVE-2026-73916 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-73916?
CVE-2026-73916 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-73916?
Yes. A fix has been recorded for CVE-2026-73916. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73916 affect?
CVE-2026-73916 affects Oracle Helidon 3.2.18, Helidon-based applications, Oracle Fusion Middleware (Helidon component). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73916?
Isolate/block Helidon HTTP endpoints, restrict network access, apply vendor patch ASAP
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker via HTTP can read, create, modify, or delete all Helidon-accessible data (confidentiality & integrity compromised).
Immediate action required
- affected>= 3.0.0 and <= 3.2.17
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.