News

USN-9179-1: Ubuntu patches over 40 CVEs in CRaC JDK 21, app restart required

Canonical releases advisory USN-9179-1: dozens of authentication and authorisation flaws in CRaC JDK 21 on Ubuntu 26.10 and 26.04 LTS.

UptimeMag editorial team · 20 November 2026 · 1 min read

USN-9179-1: Ubuntu corregge oltre 40 CVE in CRaC JDK 21, serve riavviare le app Java

Canonical published security advisory USN-9179-1 on 20 November 2026, addressing dozens of vulnerabilities in CRaC JDK 21, the Java distribution with support for Coordinated Restore at Checkpoints used to reduce startup times for production Java applications. The affected package is openjdk-21-crac, available on Ubuntu 26.10 and 26.04 LTS.

What the advisory fixes

The bulletin reports that several security issues have been corrected in CRaC JDK 21. The most serious flaw concerns the Compiler component: Albert Yang and Quang Luong discovered that the CRaC JDK 21 Compiler failed to handle certain inputs correctly, and a remote attacker could exploit the issue to cause a denial of service or execute arbitrary code (CVE-2026-114938).

The remainder of the list consists largely of authentication and authorisation flaws in the JGSS, JSSE, Libraries, Hotspot, Security, JAAS, JDBC, Networking, JAXP, ImageIO, AWT, Serviceability, JDK tools, Utility, Sound and 2D components: most allow a remote attacker to read or modify sensitive data, some only with local access. Nicholas Carlini is also credited among the researchers for an authorisation flaw in the JSSE component.

The same batch on JDK 25

The same set of over 40 CVEs had already been patched three days earlier in advisory USN-9131-1 for CRaC JDK 25, which updates packages to version 25.0.5.0.3+1-0ubuntu2, on both Ubuntu 26.10 and 26.04 LTS. The two advisories share most of the CVE identifiers, indicating that the vulnerability window spans multiple versions of the CRaC runtime in parallel.

What to do

For CRaC JDK 21, the update requires installation of a new upstream release, with security fixes accompanied by bug fixes and new features. Canonical warns that after the standard system upgrade, every running Java application must be restarted manually: updating the packages alone does not apply the patches to already-active processes. For those running containers or services with CRaC in environments with low tolerance for restarts, it's advisable to plan the maintenance window before rolling out the upgrade to production systems.

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