Release date: January 21, 2025
The full version string for this update release is 1.8.0_441-perf-b09 (where "b" means "build"). The version number is 1.8.0_441-perf.
JDK 8u441 contains IANA time zone data 2024b which contains the following changes since the previous update.
For more information, refer to Timezone Data Versions in the JRE Software.
The security baselines for the Java Runtime at the time of the release of JDK 8u441 are specified in the following table:
| Java Family Version | Security Baseline (Full Version String) |
|---|---|
| 8 | 1.8.0_441-perf-b09 |
Oracle recommends that the JDK is updated with each Critical Patch Update. In order to determine if a release is the latest, the Security Baseline page can be used to determine which is the latest version for each release family.
Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Bulletins. It is not recommended that this JDK (version 8u441) be used after the next critical patch update scheduled for April 15, 2025.
Java Management Service, available to all users, can help you find vulnerable Java versions in your systems. Java SE Subscribers and customers running in Oracle Cloud can use Java Management Service to update Java Runtimes and to do further security reviews like identifying potentially vulnerable third party libraries used by your Java programs. Existing Java Management Service user click here to log in to your dashboard. The Java Management Service Documentation provides a list of features available to everyone and those available only to customers. Learn more about using Java Management Service to monitor and secure your Java Installations.
For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 8u441) on 2025-05-15. After either condition is met (new release becoming available or expiration date reached), the JRE will provide additional warnings and reminders to users to update to the newer version. For more information, see 23.1.2 JRE Expiration Date in the Java Platform, Standard Edition Deployment Guide.
The ClassLoadingMXBean::setVerbose(boolean enabled) method will set class+load* logging on log output stdout to level info if enabled is true, and to level off otherwise. In contrast, the isVerbose method would check if exactly class+load logging was enabled at the info level on _any_ log output. This could result in counter-intuitive behavior when logging class+load=info to a file via the command-line, as it caused isVerbose to return true, even after a call to setVerbose(false) had been made. A similar problem existed for the MemoryMXBean::isVerbose method. Starting with this release, the behavior is as follows:
ClassLoadingMXBean::isVerbose will return true only if class+load* logging (note the wildcard use) has been enabled at the `info` level (or above) on the stdout log output.MemoryMXBean::isVerbose will return true only if gc logging has been enabled at the info level (or above) on the stdout log output.
| # | BugId | Component | Summary |
|---|---|---|---|
| 1 | JDK-8337066 | hotspot/compiler | Repeated call of StringBuffer.reverse with double byte string returns wrong result |
| 2 | JDK-8335709 | hotspot/compiler | C2: assert(!loop->is_member(get_loop(useblock))) failed: must be outside loop |
| 3 | JDK-8315988 | hotspot/gc | Parallel: Make TestAggressiveHeap use createTestJvm |
| 4 | JDK-8338389 | hotspot/jfr | [JFR] Long strings should be added to the string pool |
| 5 | JDK-8319818 | hotspot/runtime | Address GCC 13.2.0 warnings (stringop-overflow and dangling-pointer) |
| 6 | JDK-8340387 | hotspot/runtime | Update OS detection code to recognize Windows Server 2025 |
| 7 | JDK-8337410 | hotspot/test | The makefiles should set problemlist and adjust timeout basing on the given VM flags |