CVE-2024-24577: libgit2 is a portable C implementation of the Git core methods provided as a linkable library with a solid API

This month

HIGH 8.6REMOTEUPGRADE

CVE-2024-24577 is a high-severity flaw (CVSS 8.6) affecting libgit2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

libgit2 is a portable C implementation of the Git core methods provided as a linkable library with a solid API, allowing to build Git functionality into your application. Using well-crafted inputs to `git_index_add` can cause heap corruption that could be leveraged for arbitrary code execution. There is an issue in the `has_dir_name` function in `src/libgit2/index.c`, which frees an entry that should not be freed. The freed entry is later used an

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.6 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.5% (top 25%)
CISA exploited list	No
Weakness	CWE-122, CWE-119
Published	2024-02-06
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: libgit2

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-02-06 22:16 UTCPublished CVE record published
2026-06-17 07:14 UTCUpdated Record last modified

libgit2 libgit2 UPGRADE

Affected: < 1.6.5 · >= 1.7.0 and < 1.7.2

Fixed in: 1.6.5, 1.7.2

Safe to downgrade to: a release before 1.7.0

1. Check installed version

apt-cache policy libgit2 || rpm -q libgit2 || libgit2 --version

2. UPGRADE to 1.6.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libgit2

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libgit2

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.7.0 (Debian / Ubuntu)

apt-cache madison libgit2 sudo apt install libgit2=<VERSION_BEFORE_1.7.0> sudo apt-mark hold libgit2

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list libgit2 sudo dnf downgrade libgit2-<VERSION_BEFORE_1.7.0> sudo dnf versionlock add libgit2

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-24577?

libgit2: upgrade to 1.6.5, 1.7.2. Exact commands for each OS are on this page.

Is CVE-2024-24577 being exploited?

CVE-2024-24577 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-24577 affect?

CVE-2024-24577 affects libgit2. Severity is high (CVSS 8.6). libgit2 is a portable C implementation of the Git core methods provided as a linkable library with a solid API, allowing to build Git functionality into your application. Using well-crafted inputs to `git_index_add` can cause heap corruptio

How urgent is CVE-2024-24577?

Priority 54/100. High severity; Remotely exploitable, no login, no user action

Software pages

Git vulnerabilities

Related CVEs

CVE-2024-24575 HIGH 7.5 UPGRADE libgit2 is a portable C implementation of the Git core methods provided as a linkable library with a solid API

References

← Back to latest CVEs