# CVE-2025-54584: GitProxy packfile parsing policy bypass

Source: https://junglewise.ai/threats/cve-2025-54584-gitproxy-packfile-parsing-policy-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-07-30. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2025-54584 · Severity: medium · CVSS 4 · Published 2025-07-30

GitProxy is a tool used by organizations to enforce security policies on Git repositories by scanning and approving commits before they are merged. An attacker with push access can exploit a flaw in how GitProxy parses Git packfiles to hide malicious commits from scanning, allowing them to bypass approval policies and insert unwanted code into protected repositories.

Technologies: [@finos/git-proxy (npm)](https://junglewise.ai/threats/technologies/finos-git-proxy). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2025-54584 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-54584 being exploited in the wild.

**How severe is CVE-2025-54584?** Medium severity, with a CVSS score of 4, published 30 July 2025.

**Which products and versions are affected?** FINOS Git-Proxy <=1.19.1; @finos/git-proxy (npm) SEMVER:introduced=0,fixed=1.19.2.

**Is there a fix for CVE-2025-54584?** Yes. @finos/git-proxy (npm): upgrade to 1.19.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2025-54584 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2025-54584?** Check whether you run FINOS Git-Proxy or @finos/git-proxy (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- @finos/git-proxy (npm): upgrade to 1.19.2 or later

  ```sh
  npm install @finos/git-proxy@1.19.2
  ```


## Technical details

The vulnerability is an improper input validation flaw in parsePush.ts that uses a naive string search to locate Git packfiles by finding the last occurrence of "PACK" in the buffer. An attacker can craft a malicious packfile containing the "PACK" string within commit content (blobs or commit bodies), causing the parser to treat arbitrary data as the packfile start and ignore the actual push payload. This allows bypassing commit approval scanning and policy enforcement. The attack requires push access to the repository and considerable technical skill to craft a valid Git packfile, but no elevation of privilege or user interaction. Fixed in versions 1.19.2 and 2.0.0.

## Affected products

- FINOS git-proxy <=1.19.1

## Identifiers

- CVE-2025-54584
- GHSA-xxmh-rf63-qwjv

## Timeline

- 2025-07-30: disclosed
- 2025-07-30: patched: Patched in versions 1.19.2 and 2.0.0

## References

- [https://github.com/finos/git-proxy/security/advisories/GHSA-xxmh-rf63-qwjv](https://github.com/finos/git-proxy/security/advisories/GHSA-xxmh-rf63-qwjv)

## Related threats

- [GitProxy hidden commits injection vulnerability](https://junglewise.ai/threats/cve-2025-54586-gitproxy-hidden-commits-injection-vulnerability)
- [FINOS GitProxy authorization bypass in new branch creation](https://junglewise.ai/threats/cve-2025-54585-finos-gitproxy-authorization-bypass-in-new-branch-creation)
- [FINOS GitProxy approval bypass when pushing multiple branches](https://junglewise.ai/threats/cve-2025-54583-finos-gitproxy-approval-bypass-when-pushing-multiple-branches)