CVE-2024-20918: Oracle Java SE JDK and JRE · Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple
Affects Oracle Java SE JDK and JRESource CVE Database V5
Not known to be exploited · CVSS 7.4 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
1. Monitor Oracle's official channels closely for patches addressing CVE-2024-20918 and apply them promptly once released. 2. Until patches are available, restrict network access to Java services and APIs to trusted hosts only, using firewalls and network segmentation. 3. Review and harden configurations of Java Web Start applications and sandboxed applets to minimize loading of untrusted code. 4. Implement strict input validation and sanitization on web services interfacing with Java APIs to reduce attack vectors. 5. Employ runtime application self-protection (RASP) or Java security managers to enforce tighter access controls. 6. Conduct thorough code audits and penetration testing focusing on Java API exposure and sandbox bypass attempts. 7. Use network intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous Java API calls or exploitation attempts. 8. Educate developers and system administrators about the risks of running untrusted code and the importance of sandbox security. 9. Maintain up-to-date asset inventories to identify all systems running affected Java versions for prioritized remediation. 10. Consider deploying application-layer firewalls or API gateways to add an additional security layer around vulnerable Java services.
Description
Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Hotspot). Supported versions that are affected are Oracle Java SE: 8u391, 8u391-perf, 11.0.21, 17.0.9, 21.0.1; Oracle GraalVM for JDK: 17.0.9, 21.0.1; Oracle GraalVM Enterprise Edition: 20.3.12, 21.3.8 and 22.3.4. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as unauthorized access to critical data or complete access to all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 7.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).