CVE-2024-24575 [High] | Denial of Service in Libgit2

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_revparse_single` can cause the function to enter an infinite loop, potentially causing a Denial of Service attack in the calling application. The revparse function in `src/libgit2/revparse.c` uses a loop to parse the user-provided spec string. There is an edge-case during parsing that allows a bad actor to force the loop conditions to access arbitrary memory. Potentially, this could also leak memory if the extracted rev spec is reflected back to the attacker. As such, libgit2 versions before 1.4.0 are not affected. Users should upgrade to version 1.6.5 or 1.7.2.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	1.82%	1.44%	-0.38%
2	2026-04-19	1.97%	1.82%	-0.15%
3	2026-02-24	—	1.97%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

1.82%

1.44%

-0.38%

2026-04-19

1.97%

1.82%

-0.15%

2026-02-24

—

1.97%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.5	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	3.6	[email protected]
7.5	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.5

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

3.6

[email protected]

7.5

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

3.6

[email protected]

OS Trackers for CVE-2024-24575

vendor	priority	summary	link
`alpine`	high	CVE-2024-24575: 1 source package rows (libgit2); 7 state rows across 5 repos (3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 5, open 2.	https://security.alpinelinux.org/vuln/CVE-2024-24575
`debian`	unimportant	CVE-2024-24575 unimportant priority: Debian including 1 source packages (libgit2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2024-24575
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2024-24575
`suse`	high	CVE-2024-24575 severity important: SUSE including 31 source package names (5.1.0.6.40:libgit2-1_7-1.7.2-150600.3.3.1, git, …), 439 product×package rows across 47 product lines (Container suse/multi-linux-manager/5.1/x86_64/server, HPE Helion OpenStack 8, … (47 product lines)): Known Not Affected 423, Fixed 16.	https://www.suse.com/security/cve/CVE-2024-24575/
`ubuntu`	medium	CVE-2024-24575 medium priority: Ubuntu including 1 source packages (libgit2), 8 status rows across 8 suites (bionic, focal, jammy, mantic, noble, trusty, upstream, xenial): not-affected 6, needs-triage 1, released 1.	https://ubuntu.com/security/CVE-2024-24575

Affected software / configurations for CVE-2024-24575

Vendor	Product	Version	Raw CPE
libgit2	libgit2	>= 1.4.0, < 1.6.5	cpe:2.3:a:libgit2:libgit2::::::::
libgit2	libgit2	>= 1.7.0, < 1.7.2	cpe:2.3:a:libgit2:libgit2::::::::

References for CVE-2024-24575

URL	Tags
https://github.com/libgit2/libgit2/commit/add2dabb3c16aa49b33904dcdc07cd915efc12fa	Patch
https://github.com/libgit2/libgit2/releases/tag/v1.6.5	Release Notes
https://github.com/libgit2/libgit2/releases/tag/v1.7.2	Release Notes
https://github.com/libgit2/libgit2/security/advisories/GHSA-54mf-x2rh-hq9v	Third Party Advisory
https://lists.fedoraproject.org/archives/list/[email protected]/message/4M3P7WIEPXNRLBINQRJFXUSTNKBCHYC7/
https://lists.fedoraproject.org/archives/list/[email protected]/message/7CNDW3PF6NHO7OXNM5GN6WSSGAMA7MZE/
https://lists.fedoraproject.org/archives/list/[email protected]/message/S635BGHHZUMRPI7QOXOJ45QHDD5FFZ3S/
https://lists.fedoraproject.org/archives/list/[email protected]/message/Z6MXOX7I43OWNN7R6M54XLG6U5RXY244/
https://lists.fedoraproject.org/archives/list/[email protected]/message/ZGNHOEE2RBLH7KCJUPUNYG4CDTW4HTBT/

URL

CVE-2024-24575 | libgit2 is vulnerable to a denial of service attack in `git_revparse_single`

Exploit prediction scoring system (EPSS) score for CVE-2024-24575

Common vulnerability scoring system (CVSS) metrics for CVE-2024-24575

Weakness enumeration for CVE-2024-24575

OS Trackers for CVE-2024-24575

Affected software / configurations for CVE-2024-24575

References for CVE-2024-24575