Unauthenticated, network-accessible critical vulnerability in Oracle Helidon (enterprise Java framework). High-impact data compromise risk across enterprise apps; widely used in Oracle/Fusion Middleware environments.
CVE-2026-73924
Unauthenticated HTTP vuln in Oracle Helidon 1.4.19 enabling full data compromise
Is CVE-2026-73924 being exploited?
Not confirmed. CVE-2026-73924 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.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-73924?
CVE-2026-73924 is rated Critical with a CVSS score of 9.1. 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-73924?
Yes. A fix has been recorded for CVE-2026-73924. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73924 affect?
CVE-2026-73924 affects Oracle Helidon 1.4.19, Helidon Imperative Web Server, Oracle Fusion Middleware Helidon deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73924?
Isolate affected instances, block HTTP access, apply vendor patch/update ASAP.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker over HTTP can read, create, modify or delete all Helidon-accessible data (high confidentiality and integrity loss).
Immediate action required
- affected>= 1.0.0 and <= 1.4.18
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.