VulnerabilityPublished 22 Oct 2025Updated 30 Oct 2025

CVE-2025-53057: java-21-openjdk security update

Affects java-21-openjdkSource GCVE Database

Authoritative record:CVE-2025-53057· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium · fixed in 1:21.0.9.0.10-1.el10.alma.1 : update java-21-openjdk when convenient.

Data as of 29 Oct 2026, 23:08 UTC

CVSS 3.1 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 1:21.0.9.0.10-1.el10.alma.1, 1:21.0.9.0.10-1.el8, 1:21.0.9.0.10-1.el9.alma.1

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade the AlmaLinux to 1:21.0.9.0.10-1.el10.alma.1 (java-21-openjdk package, java-21-openjdk-demo package, java-21-openjdk-demo-fastdebug package, java-21-openjdk-demo-slowdebug package, java-21-openjdk-devel package, java-21-openjdk-devel-fastdebug package, java-21-openjdk-devel-slowdebug package, java-21-openjdk-fastdebug package, java-21-openjdk-headless package, java-21-openjdk-headless-fastdebug package, java-21-openjdk-headless-slowdebug package, java-21-openjdk-javadoc package, java-21-openjdk-javadoc-zip package, java-21-openjdk-jmods package, java-21-openjdk-jmods-fastdebug package, java-21-openjdk-jmods-slowdebug package, java-21-openjdk-slowdebug package, java-21-openjdk-src package, java-21-openjdk-src-fastdebug package, java-21-openjdk-src-slowdebug package, java-21-openjdk-static-libs package, java-21-openjdk-static-libs-fastdebug package, java-21-openjdk-static-libs-slowdebug package) or 1:21.0.9.0.10-1.el8 (java-21-openjdk package, java-21-openjdk-demo package, java-21-openjdk-demo-fastdebug package, java-21-openjdk-demo-slowdebug package, java-21-openjdk-devel package, java-21-openjdk-devel-fastdebug package, java-21-openjdk-devel-slowdebug package, java-21-openjdk-fastdebug package, java-21-openjdk-headless package, java-21-openjdk-headless-fastdebug package, java-21-openjdk-headless-slowdebug package, java-21-openjdk-javadoc package, java-21-openjdk-javadoc-zip package, java-21-openjdk-jmods package, java-21-openjdk-jmods-fastdebug package, java-21-openjdk-jmods-slowdebug package, java-21-openjdk-slowdebug package, java-21-openjdk-src package, java-21-openjdk-src-fastdebug package, java-21-openjdk-src-slowdebug package, java-21-openjdk-static-libs package, java-21-openjdk-static-libs-fastdebug package, java-21-openjdk-static-libs-slowdebug package) or 1:21.0.9.0.10-1.el9.alma.1 (java-21-openjdk package, java-21-openjdk-demo package, java-21-openjdk-demo-fastdebug package, java-21-openjdk-demo-slowdebug package, java-21-openjdk-devel package, java-21-openjdk-devel-fastdebug package, java-21-openjdk-devel-slowdebug package, java-21-openjdk-fastdebug package, java-21-openjdk-headless package, java-21-openjdk-headless-fastdebug package, java-21-openjdk-headless-slowdebug package, java-21-openjdk-javadoc package, java-21-openjdk-javadoc-zip package, java-21-openjdk-jmods package, java-21-openjdk-jmods-fastdebug package, java-21-openjdk-jmods-slowdebug package, java-21-openjdk-slowdebug package, java-21-openjdk-src package, java-21-openjdk-src-fastdebug package, java-21-openjdk-src-slowdebug package, java-21-openjdk-static-libs package, java-21-openjdk-static-libs-fastdebug package, java-21-openjdk-static-libs-slowdebug package).

Patches and advisories

access.redhat.com/errata/RHSA-2025:18824 (opens in a new tab)

Affected software

Product	Affected	Fixed in
AlmaLinux 10java-21-openjdk	Affected <1:21.0.9.0.10-1.el10.alma.1	Fixed in 1:21.0.9.0.10-1.el10.alma.1
AlmaLinux 10java-21-openjdk-demo	Affected <1:21.0.9.0.10-1.el10.alma.1	Fixed in 1:21.0.9.0.10-1.el10.alma.1
AlmaLinux 10java-21-openjdk-demo-fastdebug	Affected <1:21.0.9.0.10-1.el10.alma.1	Fixed in 1:21.0.9.0.10-1.el10.alma.1
AlmaLinux 10java-21-openjdk-demo-slowdebug	Affected <1:21.0.9.0.10-1.el10.alma.1	Fixed in 1:21.0.9.0.10-1.el10.alma.1
AlmaLinux 10java-21-openjdk-devel	Affected <1:21.0.9.0.10-1.el10.alma.1	Fixed in 1:21.0.9.0.10-1.el10.alma.1
AlmaLinux 10java-21-openjdk-devel-fastdebug	Affected <1:21.0.9.0.10-1.el10.alma.1	Fixed in 1:21.0.9.0.10-1.el10.alma.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied. Red Hat has released updated java-21-openjdk packages fixing this vulnerability. Users should update to versions 1:21.0.9.0.10-1.el8, 1:21.0.9.0.10-1.el9.alma.1, or 1:21.0.9.0.10-1.el10.alma.1 as appropriate for their system. No additional mitigation steps are indicated by the vendor advisory.

Description

A moderate security update for OpenJDK 21 addresses multiple vulnerabilities including CVE-2025-53057, which involves enhancements to certificate handling. The update fixes these issues in Red Hat Enterprise Linux distributions by providing patched versions of the java-21-openjdk package. Users should apply the update to mitigate the vulnerabilities.

Impact

The vulnerability affects the certificate handling component of OpenJDK 21, potentially impacting security related to certificate processing. The Red Hat advisory classifies the impact as moderate, indicating a security concern that does not pose critical or high risk but should be addressed to maintain system security.

Summary

The OpenJDK 21 Java Runtime Environment and Software Development Kit had security issues including CVE-2025-53057, which pertains to certificate handling enhancements. This vulnerability is addressed in the java-21-openjdk packages updated to version 1:21.0.9.0.10-1.el8, 1:21.0.9.0.10-1.el9.alma.1, and 1:21.0.9.0.10-1.el10.alma.1. The Red Hat advisory rates the update as moderate severity and recommends applying the update to affected Red Hat Enterprise Linux versions. No known exploits in the wild have been reported.

References

Community reviews

Loading reviews…