CVE-2025-58458: Jenkins Git client Plugin · CWE-538
Affects Jenkins Git client PluginSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Sep 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Jenkins Project Jenkins Git client Plugin | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-58458, European organizations should: 1) Upgrade the Jenkins Git client Plugin to a version that is not vulnerable, specifically avoiding versions 6.3.2 and earlier except 6.1.4 and 6.2.1, once a fixed version is released by the Jenkins Project. 2) Restrict Jenkins access strictly to trusted users and enforce the principle of least privilege, ensuring that only necessary personnel have Overall or Read permissions. 3) Implement network segmentation and firewall rules to limit access to Jenkins controllers from untrusted networks. 4) Monitor Jenkins logs for unusual access patterns or repeated file existence checks that could indicate exploitation attempts. 5) Consider disabling or restricting the use of the amazon-s3 protocol in Git URLs if not required. 6) Regularly audit Jenkins plugin versions and configurations as part of vulnerability management. 7) Employ multi-factor authentication (MFA) for Jenkins user accounts to reduce the risk of credential compromise. These steps go beyond generic advice by focusing on access control hardening, monitoring, and configuration adjustments specific to the vulnerability's exploitation vector.
Description
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.