USN-7674-1: OpenJDK 11 vulnerabilities

Publication date

28 July 2025

Overview

Several security issues were fixed in OpenJDK 11.


Packages

Details

It was discovered that the 2D component of OpenJDK 11 did not properly
manage memory under certain circumstances. An attacker could possibly
use this issue to cause a denial of service or execute arbitrary code.
(CVE-2025-30749, CVE-2025-50106)

VMashroor Hasan Bhuiyan discovered that the JSSE component of OpenJDK 11
did not properly manage TLS 1.3 handshakes under certain circumstances.
An attacker could possibly use this issue to obtain sensitive
information. (CVE-2025-30754)

Martin van Wingerden and Violeta Georgieva of Broadcom discovered
that the Networking component of OpenJDK 11 did not properly
manage network connections under certain circumstances. An attacker
could possibly use this issue to obtain sensitive information.
(CVE-2025-50059)

It was discovered...

It was discovered that the 2D component of OpenJDK 11 did not properly
manage memory under certain circumstances. An attacker could possibly
use this issue to cause a denial of service or execute arbitrary code.
(CVE-2025-30749, CVE-2025-50106)

VMashroor Hasan Bhuiyan discovered that the JSSE component of OpenJDK 11
did not properly manage TLS 1.3 handshakes under certain circumstances.
An attacker could possibly use this issue to obtain sensitive
information. (CVE-2025-30754)

Martin van Wingerden and Violeta Georgieva of Broadcom discovered
that the Networking component of OpenJDK 11 did not properly
manage network connections under certain circumstances. An attacker
could possibly use this issue to obtain sensitive information.
(CVE-2025-50059)

It was discovered that the Scripting component of OpenJDK 11 did not
properly manage properties under certain circumstances. An attacker
could possibly use this issue to cause a denial of service, execute
arbitrary code or bypass Java sandbox restrictions. (CVE-2025-30761)

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

Please see the following link for more information:
https://openjdk.org/groups/vulnerability/advisories/2025-07-15


Update instructions

This update uses a new upstream release, which includes additional bug fixes. After a standard system update you need to restart Java applications to make all the necessary changes.

Learn more about how to get the fixes.

The problem can be corrected by updating your system to the following package versions:

Ubuntu Release Package Version
25.04 plucky openjdk-11-jdk –  11.0.28+6-1ubuntu1~25.04.1
openjdk-11-jdk-headless –  11.0.28+6-1ubuntu1~25.04.1
openjdk-11-jre –  11.0.28+6-1ubuntu1~25.04.1
openjdk-11-jre-headless –  11.0.28+6-1ubuntu1~25.04.1
openjdk-11-jre-zero –  11.0.28+6-1ubuntu1~25.04.1
24.04 noble openjdk-11-jdk –  11.0.28+6-1ubuntu1~24.04.1  
openjdk-11-jdk-headless –  11.0.28+6-1ubuntu1~24.04.1  
openjdk-11-jre –  11.0.28+6-1ubuntu1~24.04.1  
openjdk-11-jre-headless –  11.0.28+6-1ubuntu1~24.04.1  
openjdk-11-jre-zero –  11.0.28+6-1ubuntu1~24.04.1  
22.04 jammy openjdk-11-jdk –  11.0.28+6-1ubuntu1~22.04.1
openjdk-11-jdk-headless –  11.0.28+6-1ubuntu1~22.04.1
openjdk-11-jre –  11.0.28+6-1ubuntu1~22.04.1
openjdk-11-jre-headless –  11.0.28+6-1ubuntu1~22.04.1
openjdk-11-jre-zero –  11.0.28+6-1ubuntu1~22.04.1
20.04 focal openjdk-11-jdk –  11.0.28+6-1ubuntu1~20.04.1  
openjdk-11-jdk-headless –  11.0.28+6-1ubuntu1~20.04.1  
openjdk-11-jre –  11.0.28+6-1ubuntu1~20.04.1  
openjdk-11-jre-headless –  11.0.28+6-1ubuntu1~20.04.1  
openjdk-11-jre-zero –  11.0.28+6-1ubuntu1~20.04.1  
18.04 bionic openjdk-11-jdk –  11.0.28+6-1ubuntu1~18.04.1  
openjdk-11-jdk-headless –  11.0.28+6-1ubuntu1~18.04.1  
openjdk-11-jre –  11.0.28+6-1ubuntu1~18.04.1  
openjdk-11-jre-headless –  11.0.28+6-1ubuntu1~18.04.1  
openjdk-11-jre-zero –  11.0.28+6-1ubuntu1~18.04.1  

Reduce your security exposure

Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.


Have additional questions?

Talk to a member of the team ›