[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fX9Bm4FJhXm37V-uJb8H-WwZn8_gqLdyDj5V-FkYcQOY":3},{"success":4,"data":5},true,{"vendor":6,"topVulnerabilitiesByEpss":19,"kevVulnerabilities":78,"topProductsByCves":88,"seoMetadata":90,"meta":99},{"vendorId":7,"vendorName":8,"productCount":9,"cveCount":10,"kevCount":9,"versionCount":11,"lastCveUpdate":12,"firstLetter":13,"products":14,"description":18},12267,"git-scm",1,37,657,"2025-07-08","g",[15],{"id":16,"product_name":17,"version_count":11,"cve_count":10,"kev_count":9,"last_cve_update":12},50307,"git","Git-scm is a technology vendor with 1 tracked product and 37 known security vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this vendor.",[20,29,37,43,48,53,58,64,68,73],{"cveId":21,"description":22,"publishedDate":23,"cvssScore":24,"cvssVersion":25,"severity":26,"isKev":27,"epssScore":28},"CVE-2018-17456","Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows remote code execution during processing of a recursive \"git clone\" of a superproject if a .gitmodules file has a URL field beginning with a '-' character.","2018-10-06",9.8,"v3.0","Critical",false,0.97356,{"cveId":30,"description":31,"publishedDate":32,"cvssScore":33,"cvssVersion":34,"severity":35,"isKev":27,"epssScore":36},"CVE-2021-21300","Git is an open-source distributed revision control system. In affected versions of Git a specially crafted repository that contains symbolic links as well as files using a clean\u002Fsmudge filter such as Git LFS, may cause just-checked out script to be executed while cloning onto a case-insensitive file system such as NTFS, HFS+ or APFS (i.e. the default file systems on Windows and macOS). Note that clean\u002Fsmudge filters have to be configured for that. Git for Windows configures Git LFS by default, and is therefore vulnerable. The problem has been patched in the versions published on Tuesday, March 9th, 2021. As a workaound, if symbolic link support is disabled in Git (e.g. via `git config --global core.symlinks false`), the described attack won't work. Likewise, if no clean\u002Fsmudge filters such as Git LFS are configured globally (i.e. _before_ cloning), the attack is foiled. As always, it is best to avoid cloning repositories from untrusted sources. The earliest impacted version is 2.14.2. The fix versions are: 2.30.1, 2.29.3, 2.28.1, 2.27.1, 2.26.3, 2.25.5, 2.24.4, 2.23.4, 2.22.5, 2.21.4, 2.20.5, 2.19.6, 2.18.5, 2.17.62.17.6.","2021-03-09",7.5,"v3.1","High",0.88533,{"cveId":38,"description":39,"publishedDate":40,"cvssScore":41,"cvssVersion":25,"severity":35,"isKev":27,"epssScore":42},"CVE-2017-1000117","A malicious third-party can give a crafted \"ssh:\u002F\u002F...\" URL to an unsuspecting victim, and an attempt to visit the URL can result in any program that exists on the victim's machine being executed. Such a URL could be placed in the .gitmodules file of a malicious project, and an unsuspecting victim could be tricked into running \"git clone --recurse-submodules\" to trigger the vulnerability.","2017-10-05",8.8,0.77823,{"cveId":44,"description":45,"publishedDate":46,"cvssScore":24,"cvssVersion":34,"severity":26,"isKev":27,"epssScore":47},"CVE-2014-9390","Git before 1.8.5.6, 1.9.x before 1.9.5, 2.0.x before 2.0.5, 2.1.x before 2.1.4, and 2.2.x before 2.2.1 on Windows and OS X; Mercurial before 3.2.3 on Windows and OS X; Apple Xcode before 6.2 beta 3; mine all versions before 08-12-2014; libgit2 all versions up to 0.21.2; Egit all versions before 08-12-2014; and JGit all versions before 08-12-2014 allow remote Git servers to execute arbitrary commands via a tree containing a crafted .git\u002Fconfig file with (1) an ignorable Unicode codepoint, (2) a git~1\u002Fconfig representation, or (3) mixed case that is improperly handled on a case-insensitive filesystem.","2020-02-12",0.75597,{"cveId":49,"description":50,"publishedDate":51,"cvssScore":24,"cvssVersion":34,"severity":26,"isKev":27,"epssScore":52},"CVE-2022-23521","Git is distributed revision control system. gitattributes are a mechanism to allow defining attributes for paths. These attributes can be defined by adding a `.gitattributes` file to the repository, which contains a set of file patterns and the attributes that should be set for paths matching this pattern. When parsing gitattributes, multiple integer overflows can occur when there is a huge number of path patterns, a huge number of attributes for a single pattern, or when the declared attribute names are huge. These overflows can be triggered via a crafted `.gitattributes` file that may be part of the commit history. Git silently splits lines longer than 2KB when parsing gitattributes from a file, but not when parsing them from the index. Consequentially, the failure mode depends on whether the file exists in the working tree, the index or both. This integer overflow can result in arbitrary heap reads and writes, which may result in remote code execution. The problem has been patched in the versions published on 2023-01-17, going back to v2.30.7. Users are advised to upgrade. There are no known workarounds for this issue.","2023-01-17",0.56334,{"cveId":54,"description":55,"publishedDate":56,"cvssScore":33,"cvssVersion":34,"severity":35,"isKev":27,"epssScore":57},"CVE-2023-25652","Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to `git apply --reject`, a path outside the working tree can be overwritten with partially controlled contents (corresponding to the rejected hunk(s) from the given patch). A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid using `git apply` with `--reject` when applying patches from an untrusted source. Use `git apply --stat` to inspect a patch before applying; avoid applying one that create a conflict where a link corresponding to the `*.rej` file exists.","2023-04-25",0.51883,{"cveId":59,"description":60,"publishedDate":61,"cvssScore":62,"cvssVersion":25,"severity":35,"isKev":27,"epssScore":63},"CVE-2018-11235","In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur. With a crafted .gitmodules file, a malicious project can execute an arbitrary script on a machine that runs \"git clone --recurse-submodules\" because submodule \"names\" are obtained from this file, and then appended to $GIT_DIR\u002Fmodules, leading to directory traversal with \"..\u002F\" in a name. Finally, post-checkout hooks from a submodule are executed, bypassing the intended design in which hooks are not obtained from a remote server.","2018-05-30",7.8,0.48062,{"cveId":65,"description":66,"publishedDate":51,"cvssScore":24,"cvssVersion":34,"severity":26,"isKev":27,"epssScore":67},"CVE-2022-41903","Git is distributed revision control system. `git log` can display commits in an arbitrary format using its `--format` specifiers. This functionality is also exposed to `git archive` via the `export-subst` gitattribute. When processing the padding operators, there is a integer overflow in `pretty.c::format_and_pad_commit()` where a `size_t` is stored improperly as an `int`, and then added as an offset to a `memcpy()`. This overflow can be triggered directly by a user running a command which invokes the commit formatting machinery (e.g., `git log --format=...`). It may also be triggered indirectly through git archive via the export-subst mechanism, which expands format specifiers inside of files within the repository during a git archive. This integer overflow can result in arbitrary heap writes, which may result in arbitrary code execution. The problem has been patched in the versions published on 2023-01-17, going back to v2.30.7. Users are advised to upgrade. Users who are unable to upgrade should disable `git archive` in untrusted repositories. If you expose git archive via `git daemon`, disable it by running `git config --global daemon.uploadArch false`.",0.44268,{"cveId":69,"description":70,"publishedDate":71,"cvssScore":41,"cvssVersion":25,"severity":35,"isKev":27,"epssScore":72},"CVE-2017-14867","Git before 2.10.5, 2.11.x before 2.11.4, 2.12.x before 2.12.5, 2.13.x before 2.13.6, and 2.14.x before 2.14.2 uses unsafe Perl scripts to support subcommands such as cvsserver, which allows attackers to execute arbitrary OS commands via shell metacharacters in a module name. The vulnerable code is reachable via git-shell even without CVS support.","2017-09-29",0.36003,{"cveId":74,"description":75,"publishedDate":76,"cvssScore":24,"cvssVersion":34,"severity":26,"isKev":27,"epssScore":77},"CVE-2016-2324","Integer overflow in Git before 2.7.4 allows remote attackers to execute arbitrary code via a (1) long filename or (2) many nested trees, which triggers a heap-based buffer overflow.","2016-04-08",0.18113,[79],{"cveId":80,"description":81,"publishedDate":12,"cvssScore":82,"cvssVersion":34,"severity":35,"isKev":4,"epssScore":83,"cisaVulnName":84,"cisaDateAdded":85,"cisaShortDescription":86,"cisaRequiredAction":87},"CVE-2025-48384","Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When reading a config value, Git strips any trailing carriage return and line feed (CRLF). When writing a config entry, values with a trailing CR are not quoted, causing the CR to be lost when the config is later read. When initializing a submodule, if the submodule path contains a trailing CR, the altered path is read resulting in the submodule being checked out to an incorrect location. If a symlink exists that points the altered path to the submodule hooks directory, and the submodule contains an executable post-checkout hook, the script may be unintentionally executed after checkout. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.",8,0.04379,"Git Link Following Vulnerability","2025-08-25","Git contains a link following vulnerability that stems from Git’s inconsistent handling of carriage return characters in configuration files.","Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.",[89],{"id":16,"product_name":17,"version_count":11,"cve_count":10,"kev_count":9,"last_cve_update":12},{"title":91,"metaDescription":92,"keywords":93,"structuredData":94},"Git-scm - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for Git-scm covering 1 product with 37 tracked vulnerabilities including 0 critical and 1 high-severity issues and 1 CISA KEV vulnerability. Real-time threat intelligence, CVE tracking, and security recommendations.","Git-scm vulnerabilities, Git-scm security, Git-scm CVE, Git-scm threat intelligence, vendor security analysis, cybersecurity threats, vulnerability management, CVE tracking, Git-scm KEV, Git-scm exploited vulnerabilities",{"@context":95,"@type":96,"name":97,"description":92,"url":98},"https:\u002F\u002Fschema.org","Organization","Git-scm","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Fgit-scm",{"totalProducts":9,"totalVulnerabilities":10,"kevVulnerabilities":9,"lastUpdated":12,"generatedAt":100,"apiVersion":101},"2026-10-17T12:02:12.017Z","3.0"]