<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 13:40:24 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-44973</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-44973</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: osv-scanner, Alpaquita:stream: grype, Alpaquita:stream: osv-scanner&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: osv-scanner, Alpaquita:stream: grype, Alpaquita:stream: osv-scanner&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-44973</guid>
    </item>
    <item>
      <title>Withdrawn: CLEANSTART-2026-BA39475 — Security fixes in external-secrets-fips 0.17.0-r2</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-ba39475</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: external-secrets-fips&lt;/p&gt;
&lt;p&gt;Package external-secrets-fips version 0.17.0-r2 fixes 75 vulnerabilities: CVE-2026-39820, CVE-2026-25679, CVE-2025-61726, CVE-2026-27143, CVE-2025-68121...&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: external-secrets-fips&lt;/p&gt;
&lt;p&gt;Package external-secrets-fips version 0.17.0-r2 fixes 75 vulnerabilities: CVE-2026-39820, CVE-2026-25679, CVE-2025-61726, CVE-2026-27143, CVE-2025-68121...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-ba39475</guid>
    </item>
    <item>
      <title>EUVD-2026-323556</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-323556</link>
      <description>EUVD-2026-323556</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-323556</guid>
    </item>
    <item>
      <title>fkie_cve-2026-44973</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44973</link>
      <description>&lt;p&gt;Billy is an interface filesystem abstraction for Go. Prior to 5.9.0, multiple path traversal issues exist across different components of go-billy. Insufficient path sanitization and boundary enforcement may allow crafted paths (e.g., using ..) to escape intended base directories. While go-billy was not originally designed to provide a strong security boundary, some of these issues were inconsistent across some of the built-in implementations. This results in scenarios where applications relying on go-billy for some level of isolation may inadvertently expose access to unintended filesystem locations. This vulnerability is fixed in 5.9.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Billy is an interface filesystem abstraction for Go. Prior to 5.9.0, multiple path traversal issues exist across different components of go-billy. Insufficient path sanitization and boundary enforcement may allow crafted paths (e.g., using ..) to escape intended base directories. While go-billy was not originally designed to provide a strong security boundary, some of these issues were inconsistent across some of the built-in implementations. This results in scenarios where applications relying on go-billy for some level of isolation may inadvertently expose access to unintended filesystem locations. This vulnerability is fixed in 5.9.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-44973</guid>
    </item>
    <item>
      <title>GHSA-qw64-3x98-g7q2 — go-billy has path traversal vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qw64-3x98-g7q2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/go-git/go-billy/v5, Go: github.com/go-git/go-billy/v6&lt;/p&gt;
&lt;p&gt;### Impact
Multiple path traversal issues exist across different components of `go-billy`. Insufficient path sanitization and boundary enforcement may allow crafted paths (e.g., using `..`) to escape intended base directories.&lt;/p&gt;
&lt;p&gt;While go-billy was not originally designed to provide a strong security boundary, some of these issues were inconsistent across some of the built-in implementations. This results in scenarios where applications relying on `go-billy` for some level of isolation may inadvertently expose access to unintended filesystem locations.&lt;/p&gt;
&lt;p&gt;The `osfs.ChrootOS` implementation is notably affected by this vulnerability and is now deprecated in `v5`, removed at `v6`. Users are recommended to move on to `osfs.BoundOS` instead: `osfs.New(path, WithBoundOS())`.&lt;/p&gt;
&lt;p&gt;Users requiring stronger security boundary enforcement are recommended to upgrade to `v6`, where the `osfs` implementation are backed by the [traversal-resistant](https://go.dev/blog/osroot) primitive [os.Root](https://pkg.go.dev/os#Root).&lt;/p&gt;
&lt;p&gt;### 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-billy` version.&lt;/p&gt;
&lt;p&gt;### Credits
Thanks to @faran66 and @vnykmshr for finding and separately reporting this issue privately to the go-git project. 🙇&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/go-git/go-billy/v5, Go: github.com/go-git/go-billy/v6&lt;/p&gt;
&lt;p&gt;### Impact
Multiple path traversal issues exist across different components of `go-billy`. Insufficient path sanitization and boundary enforcement may allow crafted paths (e.g., using `..`) to escape intended base directories.&lt;/p&gt;
&lt;p&gt;While go-billy was not originally designed to provide a strong security boundary, some of these issues were inconsistent across some of the built-in implementations. This results in scenarios where applications relying on `go-billy` for some level of isolation may inadvertently expose access to unintended filesystem locations.&lt;/p&gt;
&lt;p&gt;The `osfs.ChrootOS` implementation is notably affected by this vulnerability and is now deprecated in `v5`, removed at `v6`. Users are recommended to move on to `osfs.BoundOS` instead: `osfs.New(path, WithBoundOS())`.&lt;/p&gt;
&lt;p&gt;Users requiring stronger security boundary enforcement are recommended to upgrade to `v6`, where the `osfs` implementation are backed by the [traversal-resistant](https://go.dev/blog/osroot) primitive [os.Root](https://pkg.go.dev/os#Root).&lt;/p&gt;
&lt;p&gt;### 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-billy` version.&lt;/p&gt;
&lt;p&gt;### Credits
Thanks to @faran66 and @vnykmshr for finding and separately reporting this issue privately to the go-git project. 🙇&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qw64-3x98-g7q2</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-44973</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-44973</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: golang-github-go-git-go-billy, Ubuntu:24.04:LTS: golang-github-go-git-go-billy, Ubuntu:25.10: golang-github-go-git-go-billy, Ubuntu:26.04:LTS: golang-github-go-git-go-billy&lt;/p&gt;
&lt;p&gt;Billy is an interface filesystem abstraction for Go. Prior to 5.9.0, multiple path traversal issues exist across different components of go-billy. Insufficient path sanitization and boundary enforcement may allow crafted paths (e.g., using ..) to escape intended base directories. While go-billy was not originally designed to provide a strong security boundary, some of these issues were inconsistent across some of the built-in implementations. This results in scenarios where applications relying on go-billy for some level of isolation may inadvertently expose access to unintended filesystem locations. This vulnerability is fixed in 5.9.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: golang-github-go-git-go-billy, Ubuntu:24.04:LTS: golang-github-go-git-go-billy, Ubuntu:25.10: golang-github-go-git-go-billy, Ubuntu:26.04:LTS: golang-github-go-git-go-billy&lt;/p&gt;
&lt;p&gt;Billy is an interface filesystem abstraction for Go. Prior to 5.9.0, multiple path traversal issues exist across different components of go-billy. Insufficient path sanitization and boundary enforcement may allow crafted paths (e.g., using ..) to escape intended base directories. While go-billy was not originally designed to provide a strong security boundary, some of these issues were inconsistent across some of the built-in implementations. This results in scenarios where applications relying on go-billy for some level of isolation may inadvertently expose access to unintended filesystem locations. This vulnerability is fixed in 5.9.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-44973</guid>
    </item>
  </channel>
</rss>
