News

USN-9131-1: Ubuntu patches 37 CVEs in CRaC JDK 25

Canonical releases USN-9131-1: 37 CVEs in CRaC JDK 25 on Ubuntu 26.04 LTS and 26.10. Requires Java application restarts.

UptimeMag editorial team · 17 November 2026 · 2 min read

USN-9131-1: Ubuntu corregge 37 CVE in CRaC JDK 25

Canonical published USN-9131-1 on 17 November 2026, addressing 37 CVEs in the openjdk-25-crac package on Ubuntu 26.10 and Ubuntu 26.04 LTS. Anyone running production Java services based on CRaC JDK 25 has a package to update and, most importantly, applications to restart.

What changes for server administrators

CRaC (Coordinated Restore at Checkpoint) is an OpenJDK project aimed at cutting startup and warmup times for Java applications: it takes a snapshot of a running Java instance that is already warmed up, then restores it from there, skipping its own startup sequence—class loading and JIT compilation have already occurred. It is used by those serving microservices with Spring Boot, Micronaut or Quarkus who want to reduce cold start, typically in container or serverless environments.

The Ubuntu advisory lists flaws in the Security, JSSE, Networking, Compiler, JAXP, JGSS, JDBC, JAAS, Serviceability, Libraries, ImageIO, AWT, 2D, Sound and Lightweight HTTP Server components. According to the advisory, it was discovered that the Security component of CRaC JDK 25 did not correctly authenticate users, and a remote attacker could exploit this flaw to read or modify sensitive data (CVE-2026-114820). Several other flaws in Networking and JAXP can lead to denial of service or modification of sensitive data without requiring authentication.

Packages and patched versions

Ubuntu Release Package Patched version
26.10 (stonking) openjdk-25-crac-jdk, -headless, -jre, -jre-headless, -jre-zero 25.0.5.0.3+1-0ubuntu2~26.10.1
26.04 LTS (resolute) openjdk-25-crac-jdk, -headless, -jre, -jre-headless, -jre-zero 25.0.5.0.3+1-0ubuntu2~26.04.1

What you need to do

The update comes from a new upstream release with additional non-security fixes. After the standard system update, you need to manually restart each active Java application—the package does not do this automatically, and as long as the JVM process remains in memory the vulnerability remains exploitable. On systems with many JVMs running, it is worth planning a restart window rather than relying solely on apt upgrade.

For details of individual CVEs, Canonical defers to the official OpenJDK advisories dated 20, 21 and 24 October 2026.

Written with the help of artificial intelligence and checked by the editors (EU AI Act, art. 50).