gitproxy vulnerabilities and fixes

Recent CVEs affecting gitproxy, with upgrade or downgrade steps. 4 tracked.

gitproxy has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2025-07-30. Highest priority: CVE-2025-54586 (score 38/100).

• CVE-2025-54586 HIGH 7.1 UPGRADE GitProxy is an application that stands between developers and a Git remote endpoint
• CVE-2025-54585 MEDIUM 6.5 UPGRADE GitProxy is an application that stands between developers and a Git remote endpoint
• CVE-2025-54584 MEDIUM 5.7 UPGRADE GitProxy is an application that stands between developers and a Git remote endpoint (e.g., github.com)
• CVE-2025-54583 MEDIUM 6.5 UPGRADE GitProxy is an application that stands between developers and a Git remote endpoint (e.g., github.com)

FAQ

How do I fix gitproxy vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is gitproxy being exploited right now?

None of the tracked gitproxy CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which gitproxy CVE should I patch first?

CVE-2025-54586 currently ranks highest (38/100): GitProxy is an application that stands between developers and a Git remote endpoint.

RSS feed for gitproxy · ← Back to latest CVEs