openjdk-25-crac vulnerabilities

Thomas Beckers discovered that the JAXP component of CRaC JDK 25 did not
correctly authenticate certain APIs. A remote unauthenticated attacker
could possibly use this issue to gain unauthorized access to sensitive
information. (CVE-2026-22016)

It was discovered that the Networking component of CRaC JDK 25 did not
correctly authenticate certain APIs. A remote unauthenticated attacker
could possibly use this issue to cause a denial of service.
(CVE-2026-34282)

It was discovered that the JSSE component of CRaC JDK 25 did not correctly
authenticate certain APIs. A remote unauthenticated attacker could possibly
use this issue to cause a denial of service. (CVE-2026-22021)

It was discovered that the JGSS component of CRaC JDK 25 did not correctly
authenticate certain APIs. A remote attacker could possibly use this issue
to obtain sensitive information. (CVE-2026-22013)

It was discovered that the 2D component of CRaC JDK 25 did not correctly
handle certain integer arithmetic. If a user or automated system were
tricked into opening a specially crafted file, an attacker could possibly
use this issue to leak sensitive information. (CVE-2026-23865)

It was discovered that the Libraries component of CRaC JDK 25 did not
correctly authenticate certain APIs. A remote unauthenticated attacker
could possibly use this issue to cause a denial of service or gain
unauthorized modification of data privileges. (CVE-2026-22008,
CVE-2026-22018)

Ken Pyle discovered that the Security component of CRaC JDK 25 did not
correctly authenticate certain APIs. A local attacker could possibly use
this issue to leak sensitive information. (CVE-2026-22007, CVE-2026-34268)

In addition to security fixes, the updated packages contain bug fixes, new
features, and possibly incompatible changes.

Please see the following for more information:
https://openjdk.org/groups/vulnerability/advisories/2026-04-21