CVE-2025-54586: finos git-proxy · Information Exposure
Affects finos git-proxySource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 1.19.2 soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.19.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Jul 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
Upgrade finos git-proxy to 1.19.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| finos git-proxy | Affected
| Fixed in
|
AI-suggested
European organizations should immediately upgrade git-proxy to version 1.19.2 or later to remediate this vulnerability. In addition, organizations should audit their git-proxy deployment configurations and access controls to ensure that only trusted and authenticated users have commit privileges. Implement strict monitoring and logging of commit activities, especially for unusual or unreferenced commits, to detect potential injection attempts. Employ network segmentation and least privilege principles to limit access to git-proxy services. Conduct regular security reviews of repository contents to identify any unexpected or hidden commits. Integrate automated scanning tools that can detect anomalous commit patterns or unauthorized data exposure. Finally, educate developers and DevOps teams about this vulnerability and encourage prompt patching and vigilance against suspicious repository activity.
Description
GitProxy is an application that stands between developers and a Git remote endpoint. In versions 1.19.1 and below, attackers can inject extra commits into the pack sent to GitHub, commits that aren’t pointed to by any branch. Although these “hidden” commits never show up in the repository’s visible history, GitHub still serves them at their direct commit URLs. This lets an attacker exfiltrate sensitive data without ever leaving a trace in the branch view. We rate this a High‑impact vulnerability because it completely compromises repository confidentiality. This is fixed in version 1.19.2.
References
- github.com/finos/git-proxy/security/advisories/GHSA-v98g-8rqx-g93g (opens in a new tab)
- github.com/finos/git-proxy/commit/9c1449f4ec37d2d1f3edf4328bc3757e8dba2110 (opens in a new tab)
- github.com/finos/git-proxy/commit/a620a2f33c39c78e01783a274580bf822af3cc3a (opens in a new tab)
- github.com/finos/git-proxy/releases/tag/v1.19.2 (opens in a new tab)