What is GHSA-22Q8-GHMQ-63VF?

GHSA-22Q8-GHMQ-63VF is a high-severity security vulnerability in libgit2-sys (rust), affecting versions < 0.16.2. It is fixed in 0.16.2.

How severe is GHSA-22Q8-GHMQ-63VF?

GHSA-22Q8-GHMQ-63VF has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of libgit2-sys are affected by GHSA-22Q8-GHMQ-63VF?

libgit2-sys (rust) versions < 0.16.2 is affected.

Is there a fix for GHSA-22Q8-GHMQ-63VF?

Yes. GHSA-22Q8-GHMQ-63VF is fixed in 0.16.2. Upgrade to this version or later.

Is GHSA-22Q8-GHMQ-63VF exploitable, and should I be worried?

Whether GHSA-22Q8-GHMQ-63VF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-22Q8-GHMQ-63VF is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-22Q8-GHMQ-63VF in libgit2-sys

Q: How severe is GHSA-22Q8-GHMQ-63VF?

GHSA-22Q8-GHMQ-63VF has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of libgit2-sys are affected by GHSA-22Q8-GHMQ-63VF?

libgit2-sys (rust) versions < 0.16.2 is affected.

Q: Is there a fix for GHSA-22Q8-GHMQ-63VF?

Yes. GHSA-22Q8-GHMQ-63VF is fixed in 0.16.2. Upgrade to this version or later.

Q: Is GHSA-22Q8-GHMQ-63VF exploitable, and should I be worried?

Whether GHSA-22Q8-GHMQ-63VF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-22Q8-GHMQ-63VF is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-22Q8-GHMQ-63VF?

Upgrade libgit2-sys to 0.16.2 or later.

Summary

libgit2-sys affected by memory corruption, denial of service, and arbitrary code execution in libgit2

The libgit2 project fixed three security issues in the 1.7.2 release. These issues are:

The git_revparse_single function can potentially enter an infinite loop on a well-crafted input, potentially causing a Denial of Service. This function is exposed in the git2 crate via the Repository::revparse_single method.
The git_index_add function may cause heap corruption and possibly lead to arbitrary code execution. This function is exposed in the git2 crate via the Index::add method.
The smart transport negotiation may experience an out-of-bounds read when a remote server did not advertise capabilities.

The libgit2-sys crate bundles libgit2, or optionally links to a system libgit2 library. In either case, versions of the libgit2 library less than 1.7.2 are vulnerable. The 0.16.2 release of libgit2-sys bundles the fixed version of 1.7.2, and requires a system libgit2 version of at least 1.7.2.

It is recommended that all users upgrade.

Impact

GHSA-22Q8-GHMQ-63VF has a CVSS score of 8.6 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.16.2); upgrading removes the vulnerable code path.

Affected versions

libgit2-sys (< 0.16.2)

Security releases

libgit2-sys → 0.16.2 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade libgit2-sys to 0.16.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-22Q8-GHMQ-63VF? GHSA-22Q8-GHMQ-63VF is a high-severity security vulnerability in libgit2-sys (rust), affecting versions < 0.16.2. It is fixed in 0.16.2.
How severe is GHSA-22Q8-GHMQ-63VF? GHSA-22Q8-GHMQ-63VF has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of libgit2-sys are affected by GHSA-22Q8-GHMQ-63VF? libgit2-sys (rust) versions < 0.16.2 is affected.
Is there a fix for GHSA-22Q8-GHMQ-63VF? Yes. GHSA-22Q8-GHMQ-63VF is fixed in 0.16.2. Upgrade to this version or later.
Is GHSA-22Q8-GHMQ-63VF exploitable, and should I be worried? Whether GHSA-22Q8-GHMQ-63VF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-22Q8-GHMQ-63VF is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-22Q8-GHMQ-63VF? Upgrade libgit2-sys to 0.16.2 or later.

Other vulnerabilities in libgit2-sys

CVE-IDSeverityPackage summary

GHSA-M4CH-RFV5-X5G3Mediumlibgit2-sys: git2-rs fails to verify SSH keys by default