Information Exposure Affecting libgit2 package, versions <1.9.0+ds-2+deb13u1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.47% (39th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN13-LIBGIT2-18470464
  • published31 Jul 2026
  • disclosed20 Aug 2026

Introduced: 31 Jul 2026

NewCVE-2026-53586  (opens in a new tab)
CWE-200  (opens in a new tab)
CWE-522  (opens in a new tab)
CWE-601  (opens in a new tab)

How to fix?

Upgrade Debian:13 libgit2 to version 1.9.0+ds-2+deb13u1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgit2 package and not the libgit2 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

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, the built-in HTTP transport in src/libgit2/transports/http.c follows an offsite initial redirect, and handle_remote_auth and handle_auth pass transport->owner->url instead of transport->server.url to the credential callback when the redirected host returns 401 Unauthorized. A callback that scopes credentials to the original trusted URL can therefore return GIT_CREDENTIAL_USERPASS_PLAINTEXT credentials that libgit2 stores in transport->server.cred and sends as an Authorization header to the redirected host. An attacker who controls a trusted Git host or an open redirect on that host can disclose HTTP Basic credentials, personal access tokens, or equivalent credentials. This issue is fixed in versions 1.8.6 and 1.9.5.