CVE-2026-53587: libgit2 - Unauthenticated network-reachable heap out-of-bounds read in transports/smart_pkt.c:set_data

Published Aug 20, 2026
·
Updated

Last updated 13 August 2026

Other sources

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. Prior to 1.8.6 and 1.9.5, libgit2 performs a fixed-size strncmp in setdata in src/libgit2/transports/smartpkt.c without first verifying that the smart-protocol pkt-line capability buffer contains 14 bytes. A malicious Git server can make bytes after the pkt-line complete object-format=, causing formatstr to advance beyond the pkt-line and the following memchr length calculation to underflow. The resulting heap out-of-bounds walk can crash a client during the first refs-advertisement packet over HTTP, HTTPS, SSH, or the Git protocol. This issue is fixed in versions 1.8.6 and 1.9.5.

MITRE

Affected Software

1 affected componentFixes available
debian/libgit2<=1.1.0+dfsg.1-4+deb11u2, <=1.5.1+ds-1+deb12u1, <=1.9.0+ds-2
1.9.6+ds-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/libgit2 to a version that resolves this vulnerability.

    Fixed in 1.9.6+ds-1
  2. Upgrade

    Upgrade libgit2 to a version that resolves this vulnerability.

    Fixed in 1.8.6
  3. Upgrade

    Upgrade libgit2 to a version that resolves this vulnerability.

    Fixed in 1.9.5

Event History

Aug 12, 2026
Data Sourced
via Debian·10:40 PM
DescriptionAffected Software
Aug 13, 2026
Data Sourced
via Ubuntu·10:40 PM
RemedyDescriptionSeverityAffected Software
Aug 20, 2026
CVE Published
via MITRE·06:36 PM
Data Sourced
via MITRE·06:36 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which clients and connections are exposed?

Applications using libgit2 versions before 1.8.6 or 1.9.5 are exposed when they contact a malicious Git server. The crash can be triggered in the first refs-advertisement packet over HTTP, HTTPS, SSH, or the Git protocol.

2

Does exploitation require authentication or user interaction?

No. The supplied vector identifies network access, low attack complexity, no privileges, and no user interaction; a malicious Git server can send the malformed smart-protocol pkt-line.

3

What is the impact of a successful exploit?

The heap out-of-bounds walk can crash the client. The provided impact vector indicates availability impact only, with no confidentiality or integrity impact listed.

4

How can I remediate this issue?

Update libgit2 to version 1.8.6 or 1.9.5, which contain the fix.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203