<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-22T07:11:22.811681+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-53586</id>
    <title>CVE-2026-53586 — libgit2: HTTP transport can leak credentials to an offsite redirect target</title>
    <updated>2026-11-22T07:11:22.814418+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> libgit2</p>
<p>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-&gt;owner-&gt;url instead of transport-&gt;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-&gt;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.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-53586"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-8628-1</id>
    <title>USN-8628-1 — libgit2 vulnerabilities</title>
    <updated>2026-11-22T07:11:22.814482+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: libgit2, Ubuntu:Pro:16.04:LTS: libgit2, Ubuntu:Pro:18.04:LTS: libgit2, Ubuntu:Pro:20.04:LTS: libgit2, Ubuntu:Pro:22.04:LTS: libgit2, Ubuntu:24.04:LTS: libgit2, Ubuntu:26.04:LTS: libgit2</p>
<p>It was discovered that libgit2 incorrectly handled the Git Smart Protocol.
A remote attacker could possibly use this issue to cause a denial of
service or execute arbitrary code. This issue only affected Ubuntu 14.04
LTS and Ubuntu 16.04 LTS. (CVE-2016-10128)</p>
<p>It was discovered that libgit2 incorrectly handled empty packet lines in
the Git Smart Protocol. A remote attacker could possibly use this issue
to cause a denial of service. This issue only affected Ubuntu 14.04 LTS
and Ubuntu 16.04 LTS. (CVE-2016-10129)</p>
<p>It was discovered that libgit2 incorrectly handled error reporting in the
HTTP transport. A remote attacker could possibly use this issue to spoof
servers. This issue only affected Ubuntu 16.04 LTS. (CVE-2016-10130)</p>
<p>It was discovered that libgit2 incorrectly handled certain crafted "ng"
packets. A remote attacker could possibly use this issue to cause a denial
of service. This issue only affected Ubuntu 14.04 LTS, Ubuntu 16.04 LTS,
and Ubuntu 18.04 LTS. (CVE-2018-15501)</p>
<p>Krishna Ram Prakash R and Vivek Parikh discovered that libgit2 incorrectly
handled certain repository index files. A local attacker could possibly use
this issue to cause a denial of service. This issue only affected Ubuntu
18.04 LTS. (CVE-2018-8098)</p>
<p>Krishna Ram Prakash R and Vivek Parikh discovered that libgit2 incorrectly
handled certain repository index files. A local attacker could possibly use
this issue to cause a denial of service. This issue only affected Ubuntu
14.04 LTS, Ubuntu 16.04 LTS,…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-8628-1"/>
  </entry>
</feed>
