VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@finos/git-proxy: vulnerability history, versions and safety

@finos/git-proxy is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 43 releases, first recorded in Jul 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @finos/git-proxy vulnerabilities

Vulert verdict on @finos/git-proxy 2.3.0 i

Updated on 23 Oct 2026

Good news: 2.3.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 78/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Moderate

What to do: Stay on 2.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.3.0 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 30 Jul 2025 i
  • Highest CVSS 8.3 i
  • With no published fix 0 i
  • Stars 258 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @finos/git-proxy, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.3.0 17 Oct 2026 none Apache-2.0 — Details →
2.0.2 28 Sep 2026 none Apache-2.0 — Details →
2.1.2 28 Sep 2026 none Apache-2.0 — Details →
2.2.0 28 Sep 2026 none Apache-2.0 — Details →
2.1.1 08 Sep 2026 none Apache-2.0 — Details →
2.0.1 08 Sep 2026 none Apache-2.0 — Details →
2.1.0 14 Aug 2026 none Apache-2.0 — Details →
2.0.0 08 May 2026 none Apache-2.0 — Details →
2.0.0-rc.6 16 Apr 2026 none Apache-2.0 — Details →
2.0.0-rc.5 16 Mar 2026 none Apache-2.0 — Details →
2.0.0-rc.4 14 Jan 2026 none Apache-2.0 — Details →
2.0.0-rc.3 30 Sep 2025 none Apache-2.0 — Details →
2.0.0-rc.2 01 Sep 2025 none Apache-2.0 — Details →
2.0.0-rc.1 08 Aug 2025 none Apache-2.0 — Details →
1.19.2 30 Jul 2025 none Apache-2.0 — Details →
1.19.1 11 Jul 2025 H4 Apache-2.0 Yes Details →
1.19.0 10 Jul 2025 H4 Apache-2.0 Yes Details →
1.18.2 01 Jul 2025 H4 Apache-2.0 Yes Details →
1.18.0 29 Jun 2025 H4 Apache-2.0 Yes Details →
1.17.2 05 Jun 2025 H4 Apache-2.0 Yes Details →
1.17.1 04 Jun 2025 H4 Apache-2.0 Yes Details →
1.17.0 29 May 2025 H4 Apache-2.0 Yes Details →
1.14.0 20 May 2025 H4 Apache-2.0 Yes Details →
1.13.0 19 May 2025 H4 Apache-2.0 Yes Details →
1.12.0 15 May 2025 H4 Apache-2.0 Yes Details →
1.11.0 29 Apr 2025 H4 Apache-2.0 Yes Details →
1.10.0 04 Apr 2025 H4 Apache-2.0 Yes Details →
1.9.3 25 Mar 2025 H4 Apache-2.0 Yes Details →
1.9.2 24 Mar 2025 H4 Apache-2.0 Yes Details →
1.9.1 14 Mar 2025 H4 Apache-2.0 Yes Details →
1.9.0 13 Mar 2025 H4 Apache-2.0 Yes Details →
1.8.1 13 Mar 2025 H4 Apache-2.0 Yes Details →
1.8.0 20 Feb 2025 H4 Apache-2.0 Yes Details →
1.7.1 06 Dec 2024 H4 Apache-2.0 Yes Details →
1.7.0 20 Nov 2024 H4 Apache-2.0 Yes Details →
1.6.0 14 Nov 2024 H4 Apache-2.0 Yes Details →
1.5.2 13 Nov 2024 H4 Apache-2.0 Yes Details →
1.5.1 08 Nov 2024 H4 Apache-2.0 Yes Details →
1.5.0 31 Oct 2024 H4 Apache-2.0 Yes Details →
1.4.1 31 Oct 2024 H4 Apache-2.0 Yes Details →
1.4.0 25 Oct 2024 H4 Apache-2.0 Yes Details →
1.3.10 21 Oct 2024 H4 Apache-2.0 Yes Details →
1.3.9 21 Oct 2024 H4 Apache-2.0 Yes Details →
1.3.8 07 Oct 2024 H4 Apache-2.0 Yes Details →
1.3.7 03 Oct 2024 H4 Apache-2.0 Yes Details →
1.3.6 02 Oct 2024 H4 Apache-2.0 Yes Details →
1.3.5 02 Oct 2024 H4 Apache-2.0 Yes Details →
1.3.4 02 Aug 2024 H4 Apache-2.0 Yes Details →
1.3.3 29 Jul 2024 H4 Apache-2.0 Yes Details →
1.3.2 19 Jun 2024 H4 Apache-2.0 Yes Details →
1.3.1 05 Jun 2024 H4 Apache-2.0 Yes Details →
1.3.0 05 Jun 2024 H4 Apache-2.0 Yes Details →
1.2.3 29 May 2024 H4 Apache-2.0 Yes Details →
1.2.2 23 May 2024 H4 Apache-2.0 Yes Details →
1.2.1 10 May 2024 H4 Apache-2.0 Yes Details →
1.2.0 01 May 2024 H4 Apache-2.0 Yes Details →
1.1.0 26 Oct 2023 H4 Apache-2.0 Yes Details →
1.0.0 27 Jun 2023 H4 Apache-2.0 Yes Details →

All 58 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @finos/git-proxy

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2025-54583: @finos/git-proxy Approval Bypass Vulnerability 8.3 high 1.19.2 30 Jul 2025
CVE-2025-54585: @finos/git-proxy New Branch Approval Bypass Vulnerability 8.2 high 1.19.2 30 Jul 2025
CVE-2025-54586: @finos/git-proxy High-Impact Hidden Commits Injection Vulnerability 7.1 high 1.19.2 30 Jul 2025
CVE-2025-54584: GitProxy Vulnerability in PACK File Parsing 7.0 high 1.19.2 30 Jul 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @finos/git-proxy

Is @finos/git-proxy safe to use?

Vulert records 4 vulnerabilities for @finos/git-proxy in npm: 0 critical, 4 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @finos/git-proxy's Vulert package health score?

Vulert scores @finos/git-proxy 78/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @finos/git-proxy affected?

No. 2.3.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does @finos/git-proxy have?

4 vulnerabilities are recorded for @finos/git-proxy in the npm ecosystem: 0 critical, 4 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @finos/git-proxy vulnerabilities disclosed?

0 vulnerabilities were recorded for @finos/git-proxy in the last 12 months, and the oldest entry in this database dates to 30 Jul 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @finos/git-proxy are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @finos/git-proxy for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @finos/git-proxy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.