Back to vendor advisories
Ubuntu Security NoticesUSN-9015-1

USN-9015-1: OpenJDK 21 vulnerabilities

Severity not listed 20 CVEs Published Nov 9, 2026 at 6:01 PM UTC

Summary

It was discovered that the Security component of OpenJDK 21 did not correctly authenticate users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-83374)

It was discovered that the JSSE component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-83376)

It was discovered that the Compiler component of OpenJDK 21 did not correctly authorize users. An unauthenticated remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-83378)

It was discovered that the JAAS component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-83380)

It was discovered that the Security component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-83381)

It was discovered that the JDBC component of OpenJDK 21 did not correctly authenticate users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-83387)

It was discovered that the Networking component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service or modify sensitive data. (CVE-2026-83395)

It was discovered that the JAXP component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-83400)

It was discovered that the JAXP component of OpenJDK 21 did not correctly authenticate users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-87290)

It was discovered that the Networking component of OpenJDK 21 did not correctly authorize users. An unauthenticated remote attacker could possibly use this issue to read sensitive data. (CVE-2026-87291)

It was discovered that the Networking component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-87292)

It was discovered that the Security component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-87294)

It was discovered that the JAXP component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-87367)

It was discovered that the Networking component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-91332)

It was discovered that the Security component of OpenJDK 21 did not correctly authorize users. An unauthenticated remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91333)

It was discovered that the ImageIO component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-91334)

It was discovered that the AWT component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-91335)

It was discovered that the JSSE component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-91373)

It was discovered that the Serviceability component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91374)

It was discovered that the Libraries component of OpenJDK 21 did not correctly authenticate users. A local attacker could possibly use this issue to modify sensitive data. (CVE-2026-91375)

It was discovered that the JDK tools component of OpenJDK 21 did not correctly authenticate users. A local attacker could possibly use this issue to modify sensitive data. (CVE-2026-91379)

It was discovered that the Utility component of OpenJDK 21 did not correctly authorize users. A local attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91380)

It was discovered that the Networking component of OpenJDK 21 did not correctly authenticate users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-91394)

It was discovered that the Serviceability component of OpenJDK 21 did not correctly authorize users. A local attacker could possibly use this issue to cause a denial of service or modify sensitive data. (CVE-2026-91397)

It was discovered that the Networking component of OpenJDK 21 did not correctly authenticate users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-91398)

It was discovered that the Sound component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-91400)

It was discovered that the JSSE component of OpenJDK 21 did not correctly authenticate users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91403)

It was discovered that the Libraries component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-91410)

It was discovered that the 2D component of OpenJDK 21 did not correctly authenticate users. A remote attacker could possibly use this issue to cause a denial of service or read or modify sensitive data. (CVE-2026-91415)

It was discovered that the ImageIO component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-91418)

It was discovered that the Networking component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-91451, CVE-2026-91452)

It was discovered that the Lightweight HTTP Server component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-91453)

It was discovered that the JSSE component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-91461)

It was discovered that the JGSS component of OpenJDK 21 did not correctly authenticate users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-91462)

It was discovered that the JGSS component of OpenJDK 21 did not correctly authenticate users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-91463, CVE-2026-91464)

It was discovered that the Compiler component of OpenJDK 21 did not correctly authorize users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91487)

It was discovered that the Libraries component of OpenJDK 21 did not correctly authenticate users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-101516)

It was discovered that the Security component of OpenJDK 21 did not correctly authenticate users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-114820)

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-10-20 https://openjdk.org/groups/vulnerability/advisories/2026-10-21 https://openjdk.org/groups/vulnerability/advisories/2026-10-24

Products covered

A separate affected-products list was not included in the collected bulletin.

Remediation

Separate remediation guidance was not included in the collected bulletin.

CVEs in this advisory 20

Updates

  1. Published by Ubuntu

    The publication date reported by the vendor.

  2. Added to SecurityAlert

    We collected the advisory from the official source.