<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T14:58:27.008323+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2024-7598</id>
    <title>CVE-2024-7598 — Network restriction bypass via race condition during namespace termination</title>
    <updated>2026-10-07T14:58:27.409003+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Kubernetes kube-apiserver</p>
<p>A security issue was discovered in Kubernetes where a malicious or compromised pod could bypass network restrictions enforced by network policies during namespace deletion. The order in which objects are deleted during namespace termination is not defined, and it is possible for network policies to be deleted before the pods that they protect. This can lead to a brief period in which the pods are running, but network policies that should apply to connections to and from the pods are not enforced.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2024-7598"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/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-10-07T14:58:27.409074+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://cve.radiocsirt.org/vuln/ghsa-389r-gv7p-r3rp"/>
  </entry>
</feed>
