File-existence disclosure via JGit Amazon S3 errors
Published Sep 3, 2025 · Updated Nov 4, 2025
Information disclosure in Git client 6.3.2 and earlier, except 6.1.4 and 6.2.1, lets remote authenticated users test controller file existence. JGit interprets the amazon-s3 URL authority as a credential-file path, and URL form validation returns distinguishable errors depending on whether that path exists. Reachability requires a plugin exposing the validation and suitable permissions; command-line Git-only instances, the default, are unaffected.
Summary
What happened
Information disclosure in Git client 6.3.2 and earlier, except 6.1.4 and 6.2.1, lets remote authenticated users test controller file existence. JGit interprets the amazon-s3 URL authority as a credential-file path, and URL form validation returns distinguishable errors depending on whether that path exists. Reachability requires a plugin exposing the validation and suitable permissions; command-line Git-only instances, the default, are unaffected.
The record
- CVE
- CVE-2025-58458
- Published
- Sep 3, 2025
- Updated
- Nov 4, 2025
- Vendor
- Jenkins Project
- Product
- Git client
- Classifications
- CWE-538, CWE-200, T1083
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 3, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo