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.
CVE-2026-53586
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
August 20, 2026
Last Modified
August 21, 2026
Advisory Details (6)
Auto-updated Aug 20, 2026libgit2 v1.9.5
Patch available: libgit2/libgit2 v1.9.5
https://github.com/libgit2/libgit2/releases/tag/v1.9.5libgit2 v1.8.6
Patch available: libgit2/libgit2 v1.8.6
https://github.com/libgit2/libgit2/releases/tag/v1.8.6commit c1507abc4464 (libgit2/libgit2)
Patch available: libgit2/libgit2 v1.8.6 (contains commit c1507abc4464)
https://github.com/libgit2/libgit2/commit/c1507abc44647b3acd832a33a5b1c8c9f5ba8821commit af2b29ad0a74 (libgit2/libgit2)
Patch available: libgit2/libgit2 v1.9.5 (contains commit af2b29ad0a74)
https://github.com/libgit2/libgit2/commit/af2b29ad0a74d5bac9751376879ddaf848136d3bcommit 07de6a7e438f (libgit2/libgit2)
Fix landed in libgit2/libgit2 commit 07de6a7e438f — awaiting tagged release
https://github.com/libgit2/libgit2/commit/07de6a7e438f95ac9a6efd3222a82117e871ed27HTTP transport can leak credentials to an offsite redirect target · Advisory · libgit2/libgit2 · GitHub
https://github.com/libgit2/libgit2/security/advisories/GHSA-2889-x8f6-mc4xVendor Advisories for CVE-2026-53586(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | libgit2-main-1.9.7-1.hum1 | 2026-08-25 | redhat |
| ubuntu | libgit2-fixtures (1.1.0+dfsg.1-4.1ubuntu0.1+esm1) @ jammy | 2026-08-25 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 21× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 18:31 UTCEG score recompute
- 2026-08-25 18:31 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 19:29 UTCEG score recompute
- 2026-08-24 19:29 UTCVendor advisory
- 2026-08-23 20:28 UTCEG score recompute
- 2026-08-23 20:28 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 21:27 UTCEG score recompute
- 2026-08-22 21:27 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 22:26 UTCEG score recompute
- 2026-08-21 22:26 UTCVendor advisory
- 2026-08-21 21:54 UTCEG score recompute
- 2026-08-21 21:54 UTCVendor advisory
- 2026-08-21 18:19 UTCVendor advisory
- 2026-08-20 19:18 UTCEG score recompute
- 2026-08-20 19:18 UTCVendor advisory
- 2026-08-20 18:52 UTCEG score recompute
- 2026-08-20 18:52 UTCVendor advisory
- 2026-08-20 18:51 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-53586?
When was CVE-2026-53586 disclosed?
Is CVE-2026-53586 actively exploited?
What is the CVSS score of CVE-2026-53586?
How do I remediate CVE-2026-53586?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-53586
Is Your Infrastructure Affected by CVE-2026-53586?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.