CVE-2025-30752 is a vulnerability identified in Oracle Java SE and Oracle GraalVM for JDK, specifically affecting version 24.0.1 of these products. The vulnerability resides in the compiler component of these Java platforms. It allows an unauthenticated attacker with network access through multiple protocols to potentially cause a partial denial of service (DoS) condition. The vulnerability is characterized as difficult to exploit, requiring network access but no authentication or user interaction. It primarily impacts Java deployments that run untrusted code, such as sandboxed Java Web Start applications or sandboxed Java applets, which rely on the Java sandbox for security. Importantly, this vulnerability does not affect server-side Java deployments that only run trusted code installed by administrators. The CVSS 3.1 base score is 3.7, indicating a low severity level, with the impact limited to availability (partial DoS). The vulnerability is linked to CWE-400, which relates to uncontrolled resource consumption, suggesting that the attack may exploit resource exhaustion to degrade service availability. No known exploits are currently reported in the wild, and no patches have been linked yet. The attack vector is network-based with high attack complexity, no privileges required, and no user interaction needed, but the scope remains unchanged, and there is no impact on confidentiality or integrity.

For European organizations, the impact of CVE-2025-30752 is relatively limited due to its low severity and partial denial of service effect. However, organizations that utilize Oracle Java SE or Oracle GraalVM for JDK version 24.0.1 in client-side environments—particularly those that run sandboxed Java Web Start applications or applets loading untrusted code—may experience service disruptions or degraded application availability. This could affect business operations relying on Java-based client applications, especially in sectors where such applications are used for critical workflows or user interactions. Since the vulnerability does not affect server-side deployments running trusted code, backend systems and enterprise servers are less likely to be impacted. The absence of known exploits in the wild further reduces immediate risk. Nonetheless, organizations should be aware that partial DoS conditions can lead to reduced productivity and potential indirect impacts on service delivery and user experience.

European organizations should take the following specific mitigation steps: 1) Identify and inventory all deployments of Oracle Java SE and Oracle GraalVM for JDK, focusing on version 24.0.1, particularly in client-side environments running sandboxed applications. 2) Restrict network access to Java client applications from untrusted networks where possible, implementing network segmentation and firewall rules to limit exposure to multiple protocols that could be exploited. 3) Where feasible, disable or limit the use of Java Web Start and applets that load untrusted code, or migrate to alternative technologies that do not rely on sandboxed Java code execution. 4) Monitor application and system logs for unusual resource consumption patterns indicative of attempted exploitation of resource exhaustion vulnerabilities. 5) Stay updated with Oracle’s security advisories for patches or updates addressing this vulnerability and plan timely application of patches once available. 6) Educate users and administrators about the risks of running untrusted Java code and enforce strict policies on code execution within sandboxed environments. These measures go beyond generic advice by focusing on network controls, application inventory, and operational policies tailored to the nature of this vulnerability.