<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T00:58:43.080923+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2026-25680</id>
    <title>CVE-2026-25680 — Invoking denial of service when parsing arbitrary HTML in golang.org/x/net/html</title>
    <updated>2026-09-29T00:58:46.254094+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> golang.org/x/net/html</p>
<p>Parsing arbitrary HTML can consume excessive CPU time, possibly leading to denial of service.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-25680"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-389r-gv7p-r3rp</id>
    <title>GHSA-389r-gv7p-r3rp — go-git's improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git</title>
    <updated>2026-09-29T00:58:46.254265+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/go-git/go-git/v6, Go: github.com/go-git/go-git/v5</p>
<p>### Impact
`go-git` may parse malformed Git objects in a way that differs from upstream Git. When `commit` or `tag` objects contain ambiguous or malformed headers, `go-git`’s decoded representation may expose values differently from how Git itself would interpret or reject the same object.</p>
<p>Additionally, `go-git`’s commit signing and verification logic operates over commit data reconstructed from `go-git`’s parsed representation rather than the original raw object bytes. As a result, `go-git` may sign or verify a commit payload that is not byte-for-byte equivalent to the object stored in the repository.</p>
<p>This can cause a signature to appear valid for a commit whose displayed or effective metadata differs from the object that was intended to be signed.</p>
<p>### Patches
Users should upgrade to a patched version in order to mitigate this vulnerability. Versions prior to v5 are likely to be affected, users are recommended to upgrade to a supported `go-git` version.</p>
<p>### Credit</p>
<p>Thanks to @bugbunny-research (https://bugbunny.ai/) for reporting this to `sigstore/gitsign`, and to @wlynch, @patzielinski and @adityasaky for coordinating the disclosure with the `go-git` project. :bow: :1st_place_medal:</p>
<p>Thanks to @wayphinder for reporting this to the `go-git` project. :bow:</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-389r-gv7p-r3rp"/>
  </entry>
</feed>
