Back to vendor advisories
Ubuntu Security NoticesUSN-8689-1

USN-8689-1: OpenJDK 26 vulnerabilities

Severity not listed 9 CVEs Published Aug 31, 2026 at 12:41 AM UTC

Summary

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

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

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

It was discovered that the 2D component of OpenJDK 26 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-47021, CVE-2026-47059)

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

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

It was discovered that the Libraries component of OpenJDK 26 did not correctly authenticate users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-47063) Lian Owen discovered that the 2D (Little CMS) component of OpenJDK 26 did not correctly handle certain integer arithmetic. An attacker could possibly use this issue to cause a denial of service. (CVE-2026-41254)

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 9

Updates

  1. Published by Ubuntu

    The publication date reported by the vendor.

  2. Added to SecurityAlert

    We collected the advisory from the official source.

  3. Confirmed at the source

    Our collector saw this advisory during a later source check.