7.1

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2025-54586

CVE-2025-54586: GitProxy Hidden Commits Injection

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" src="https://github.com/user-attachments/assets/abf459a9-310b-4819-a989-797c7e871790" />

PoC

Prerequisites

A GitHub Personal Access Token stored in ~/.github-test-pat.
A test repository also registered in git-proxy, e.g. your-org/test-repo.git, to which you have push rights.

1. Prepare the “visible” and “hidden” commits

# Clone the test repository
git clone http://localhost:8000/your-org/test-repo.git
cd test-repo

# 1. Record the original HEAD
ORIG_COMMIT=$(git rev-parse HEAD)

# 2. Create branch 'foo' and add a visible commit
git checkout -b foo
echo "visible commit" >> file.txt
git add file.txt
git commit -m "Visible commit"
VISIBLE_COMMIT=$(git rev-parse HEAD)

# 3. Go back to the original commit and create a hidden-branch
git checkout $ORIG_COMMIT
git checkout -b hidden-branch
echo "hidden change" > hidden.txt
git add hidden.txt
git commit -m "Hidden commit"
HIDDEN_COMMIT=$(git rev-parse HEAD)

# Return to 'foo'
git checkout foo

2. Push only the visible commit to branch `foo`

git push --set-upstream origin foo
# An authorized user approves this push via your normal review workflow

Miggo Vulnerability Database

→

CVE-2025-54586

CVE-2025-54586:

7.1

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
@finos/git-proxy	npm	<= 1.19.1	1.19.2

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability, 'GitProxy Hidden Commits Injection', allows an attacker to inject commits into a repository that are not referenced by any branch, making them hidden from the normal git history. This is possible because the git-proxy was not verifying that the commits contained within the pushed packfile matched the commits that were supposed to be pushed according to the git ref-update information.

The analysis of the patches reveals that the vulnerability is addressed by introducing a new validation step, checkHiddenCommits, into the push processing chain. The functions that were active in the processing chain before this new validation step, and were responsible for handling the user's push data, are the ones considered vulnerable.

Two main functions have been identified:

parsePush.exec: This function is the entry point for parsing the push request. Its original implementation was too simplistic and did not correctly parse and prepare the data for the necessary validation. It was a key enabler of the vulnerability because it didn't set up the necessary checks.
writePack.exec: This function takes the user-provided packfile and writes it to the repository using git receive-pack. This is the function that directly processes the malicious data containing the hidden commits. Before the patch, it did so without any verification.

During an exploit, both of these functions would be called. parsePush.exec would first parse the malicious request, and then writePack.exec would write the malicious packfile to disk. The vulnerability is the absence of a check between these two steps. Therefore, both are critical runtime indicators for this vulnerability.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.

7.1

-

Basic Information

Basic Information

Concerned about an active attack path?

CVE-2025-54586: GitProxy Hidden Commits Injection

Summary

Details

PoC

Prerequisites

1. Prepare the “visible” and “hidden” commits

2. Push only the visible commit to branch foo

CVE-2025-54586:

7.1

-

Basic Information

Basic Information

Is this CVE running in your environment?

Technical Details

Technical Details

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Vulnerability IntelligenceMiggo AI

Unlock WAF rules for this CVE

WAF Protection Rules

WAF Rule

Reasoning

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Basic Information

Basic Information

Technical Details

7.1

7.1

CVE-2025-54586: GitProxy Hidden Commits Injection

Summary

Details

PoC

Prerequisites

1. Prepare the “visible” and “hidden” commits

2. Push only the visible commit to branch foo

3. Build and push a pack containing the hidden commit

4. Verify the hidden commit

Impact

2. Push only the visible commit to branch `foo`

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI

2. Push only the visible commit to branch `foo`