CVE-2025-53103 | JUnit OpenTestReportGeneratingListener can leak Git credentials

JUnit is a testing framework for Java and the JVM. From version 5.12.0 to 5.13.1, JUnit's support for writing Open Test Reporting XML files can leak Git credentials. The impact depends on the level of the access token exposed through the OpenTestReportGeneratingListener. If these test reports are published or stored anywhere public, then there is the possibility that a rouge attacker can steal the token and perform elevated actions by impersonating the user or app. This issue as been patched in version 5.13.2.

Published: 2025-07-01 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-53103 is rated Low Risk (23.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-53103

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-07-02 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-53103

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.8 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 0.6 5.2 [email protected]

Weakness enumeration for CVE-2025-53103

GitHub Security Advisory for CVE-2025-53103

GHSA-m43g-m425-p68x · Severity: medium · Ecosystem: maven — junit-platform-reporting can leak Git credentials through its OpenTestReportGeneratingListener

OS Trackers for CVE-2025-53103

vendor priority summary link
debian unimportant CVE-2025-53103 unimportant priority: Debian including 1 source packages (junit5), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-53103
redhat medium — https://access.redhat.com/security/cve/CVE-2025-53103
suse high CVE-2025-53103 severity important: SUSE including 7 source package names (junit, junit-javadoc, …), 26 product×package rows across 20 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (20 product lines)): Known Not Affected 26. https://www.suse.com/security/cve/CVE-2025-53103/
ubuntu medium CVE-2025-53103 medium priority: Ubuntu including 1 source packages (junit5), 7 status rows across 7 suites (focal, jammy, noble, oracular, plucky, questing, upstream): needs-triage 4, ignored 2, not-affected 1. https://ubuntu.com/security/CVE-2025-53103

Affected software / configurations for CVE-2025-53103

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-53103

cvelogic Threat Intelligence