Vulnerability Database · RubyGems · git · Version
git 1.2.5
1.2.5 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 5.6.0.
Critical 1 High 2 Medium 0 Low 0 Unrated 0
-
Released 17 Oct 2009
Licence MIT
Also known from other sources 3
Newer releases 99
Database updated 23/Oct/2026
Release and licence data published by RubyGems. 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 Vulnerabilities affecting this version
git 1.2.5 vulnerabilities
3 vulnerabilities cover git 1.2.5. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2022-25648: Command Injection in ruby-git | 9.8 critical | 1.11.0 | 20 Apr 2022 |
| CVE-2022-47318: Code Injection in Ruby Git | 8.0 high | 1.13.0 | 17 Jan 2023 |
| CVE-2022-46648: Remote Code Execution Vulnerability in ruby-git | 8.0 high | 1.13.0 | 09 Jan 2023 |
Looking for another version, or everything Vulert holds for git?
Questions
About git 1.2.5
Is git 1.2.5 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover git 1.2.5: 1 critical, 2 high, 0 medium and 0 low. The upgrade Vulert recommends is 5.6.0, and each entry above names the fixed version to move to.
Which version of git should I use instead of 1.2.5?
5.6.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 1.2.5 the latest release of git?
No. 1.2.5 was published 17 Oct 2009, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor git for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the git version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.