CVE-2025-58458

In Jenkins Git client Plugin 6.3.2 and earlier, except 6.1.4 and 6.2.1, Git URL field form validation responses differ based on whether the specified file path exists on the controller when specifying `amazon-s3` protocol for use with JGit, allowing attackers with Overall/Read permission to check for the existence of an attacker-specified file path on the Jenkins controller file system.

Published: 2025-09-03 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-58458 is rated Low Risk (24.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.29%). 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-58458

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 2026-06-15 0.06% 0.29% +0.23%
2 2026-02-11 0.05% 0.06% +0.01%
3 2026-01-30 — 0.05% —

Full EPSS history (7 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-58458

GitHub Security Advisory for CVE-2025-58458

GHSA-g2pq-9jr7-w6gv · Severity: medium · Ecosystem: maven — Jenkins Git client Plugin file system information disclosure vulnerability

OS Trackers for CVE-2025-58458

vendor priority summary link
alpine — CVE-2025-58458: 1 source package rows (jenkins); 5 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 5. https://security.alpinelinux.org/vuln/CVE-2025-58458

Affected software / configurations for CVE-2025-58458

Vendor Product Version Raw CPE
jenkins git_client <= 6.1.3 cpe:2.3:a:jenkins:git_client:*:*:*:*:*:jenkins:*:*
jenkins git_client >= 6.3.0, <= 6.3.2 cpe:2.3:a:jenkins:git_client:*:*:*:*:*:jenkins:*:*
jenkins git_client 6.2.0 cpe:2.3:a:jenkins:git_client:6.2.0:*:*:*:*:jenkins:*:*

References for CVE-2025-58458

cvelogic Threat Intelligence