CVE-2025-53057VulnerabilityPublished 22 Oct 2025Updated 11 Oct 2026

SUSE · security update for java-17-openjdk

Affects SUSESource GCVE Database

Mentioned vulnerabilities

CVE-2025-53066

Authoritative record:CVE-2025-53057· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

5.9Medium

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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

Affected software

Product	Affected	Fixed in
Red Hatredhat/java-17-openjdk`pkg:rpm/redhat/java-17-openjdk`Other threats	Affected *	Fixed in–

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

AI-suggested

A security update is available and should be applied to affected systems. Red Hat advises ensuring all previously released errata relevant to your system are applied before updating. Detailed update instructions are available at https://access.redhat.com/articles/11258. Applying this update will remediate the vulnerabilities CVE-2025-53066 and CVE-2025-53057. No additional mitigation steps are indicated by the vendor advisory.

Description

A security update has been released for the java-17-openjdk packages used in Red Hat Enterprise Linux and SUSE distributions. The update addresses two vulnerabilities: CVE-2025-53066 related to path factories and CVE-2025-53057 related to certificate handling. The update also includes bug fixes related to build packaging across multiple Red Hat Enterprise Linux releases. The security impact is rated as moderate by Red Hat Product Security. No CVSS score is provided in the advisory. The update is available for various Red Hat Enterprise Linux 8 and 9 versions and architectures.

Impact

The vulnerabilities addressed potentially affect the security of Java applications running on OpenJDK 17 by improving path factory handling and certificate processing. These issues could lead to security weaknesses if left unpatched. The update mitigates these risks, reducing the attack surface related to path and certificate handling in the JDK. Red Hat classifies the impact as moderate, indicating that exploitation could have a limited to moderate effect on confidentiality, integrity, or availability.

CWE-838Inappropriate Encoding for Output Context (opens in a new tab)
Base weakness
The product uses or specifies an encoding when generating output to a downstream component, but the specified encoding is not the same as the encoding that is expected by the downstream component.
Implementation · Output Encoding
Use context-aware encoding. That is, understand which encoding is being used by the downstream component, and ensure that this encoding is used. If an encoding can be specified, do so, instead of assuming that the default encoding is the same as the default being assumed by the downstream component.
Architecture and Design · Output Encoding
Where possible, use communications protocols or data formats that provide strict boundaries between control and data. If this is not feasible, ensure that the protocols or formats allow the communicating components to explicitly state which encoding/decoding method is being used.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Content Security Policy (opens in a new tab)
OWASP ASVS 4.0.3
V14.4.6 (opens in a new tab)
V14.4.4 (opens in a new tab)
V14.4.2 (opens in a new tab)
Attack patterns
Generic Cross-Browser Cross-Domain Theft (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Oct 2026, 22:22 UTC

WeaknessesCWE-838

Technical details

References

Community reviews

Related threats