GitProxy Hidden Commits Injection

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

EPSS

• CVE-2025-54586: 0.41% estimated exploitation activity in the next 30 days; percentile 35.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary An attacker 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. Details The proxy currently trusts only the ref‑update line (oldOid → newOid) and doesn't inspect the packfile’s contents Because the code only runs git rev-list oldOid..newOid to compute introducedCommits but never checks which commits actually arrived in the pack, a malicious client can append extra commits. Those “hidden” commits won’t be pointed to by any branch but GitHub still stores and serves them by SHA. <img width="2556" height="744" alt="Screenshot 2025-07-16 at 12 29 19"…

Published by the source

30 Jul 2025, 16:40 UTC

Last modified by the source

31 Jul 2025, 12:02 UTC

Source last checked

26 Oct 2026, 12:37 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-v98g-8rqx-g93g

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-v98g-8rqx-g93g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-54586

Advisory: GitProxy Hidden Commits Injection
IDs: CVE-2025-54586, GHSA-v98g-8rqx-g93g
Record: https://patchnext.com/advisories/cve-2025-54586 (revision 2, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @finos/git-proxy 1.19.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @finos/git-proxy: affected <= 1.19.1; fixed in 1.19.2

## Suggested inspection (read-only)
- `npm ls @finos/git-proxy --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @finos/git-proxy.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-v98g-8rqx-g93g (OSV record GHSA-v98g-8rqx-g93g lists affected ranges: npm @finos/git-proxy >=0 <1.19.2 (fixed))
- Verified: https://github.com/advisories/GHSA-v98g-8rqx-g93g (GitHub-reviewed advisory GHSA-v98g-8rqx-g93g lists affected ranges: npm @finos/git-proxy >=0 <=1.19.1)

Commands are suggestions: review each one before running it.