<?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>Mon, 05 Oct 2026 20:27:00 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-277344</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-277344</link>
      <description>EUVD-2026-277344</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-277344</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33353</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33353</link>
      <description>&lt;p&gt;Soft Serve is a self-hostable Git server for the command line. From version 0.6.0 to before version 0.11.6, an authorization flaw in repo import allows any authenticated SSH user to clone a server-local Git repository, including another user&amp;#39;s private repo, into a new repository they control. This issue has been patched in version 0.11.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Soft Serve is a self-hostable Git server for the command line. From version 0.6.0 to before version 0.11.6, an authorization flaw in repo import allows any authenticated SSH user to clone a server-local Git repository, including another user&amp;#39;s private repo, into a new repository they control. This issue has been patched in version 0.11.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-33353</guid>
    </item>
    <item>
      <title>GHSA-xgxp-f695-6vrp — In Soft Serve, an authenticated repo import can clone server-local private repositories</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xgxp-f695-6vrp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/charmbracelet/soft-serve&lt;/p&gt;
&lt;p&gt;### Summary
An authorization flaw in `repo import` allows any authenticated SSH user to clone a server-local Git repository, including another user&amp;#39;s private repo, into a new repository they control. This breaks the private-repository confidentiality boundary and should be treated as High severity.&lt;/p&gt;
&lt;p&gt;### Details
Repo import checks authorization only for the destination repository name, not for the source remote. The destination-side authorization comes from [`pkg/ssh/cmd/cmd.go:172`](https://github.com/charmbracelet/soft-serve/blob/main/pkg/ssh/cmd/cmd.go#L172), which calls [`pkg/backend/user.go:46`](https://github.com/charmbracelet/soft-serve/blob/main/pkg/backend/user.go#L46). If the destination repo does not already exist, any authenticated user is granted `ReadWriteAccess` at [`pkg/backend/user.go:94`](https://github.com/charmbracelet/soft-serve/blob/main/pkg/backend/user.go#L94).&lt;/p&gt;
&lt;p&gt;The import command then passes the user-controlled `REMOTE` into [`pkg/backend/repo.go:102`](https://github.com/charmbracelet/soft-serve/blob/main/pkg/backend/repo.go#L102). In vulnerable `HEAD`, `git.Clone(remote, rp, copts)` is reached without validating that `remote` is actually a network remote. As a result, a user can supply a server filesystem path such as `$DATA_PATH/repos/secret.git` and cause the server to clone its own local bare repository into a new repo owned by the attacker.&lt;/p&gt;
&lt;p&gt;The relevant vulnerable flow is:
- [`pkg/ssh/cmd/import.go`](https://github.com/charmbracelet/soft-serve/b…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/charmbracelet/soft-serve&lt;/p&gt;
&lt;p&gt;### Summary
An authorization flaw in `repo import` allows any authenticated SSH user to clone a server-local Git repository, including another user&amp;#39;s private repo, into a new repository they control. This breaks the private-repository confidentiality boundary and should be treated as High severity.&lt;/p&gt;
&lt;p&gt;### Details
Repo import checks authorization only for the destination repository name, not for the source remote. The destination-side authorization comes from [`pkg/ssh/cmd/cmd.go:172`](https://github.com/charmbracelet/soft-serve/blob/main/pkg/ssh/cmd/cmd.go#L172), which calls [`pkg/backend/user.go:46`](https://github.com/charmbracelet/soft-serve/blob/main/pkg/backend/user.go#L46). If the destination repo does not already exist, any authenticated user is granted `ReadWriteAccess` at [`pkg/backend/user.go:94`](https://github.com/charmbracelet/soft-serve/blob/main/pkg/backend/user.go#L94).&lt;/p&gt;
&lt;p&gt;The import command then passes the user-controlled `REMOTE` into [`pkg/backend/repo.go:102`](https://github.com/charmbracelet/soft-serve/blob/main/pkg/backend/repo.go#L102). In vulnerable `HEAD`, `git.Clone(remote, rp, copts)` is reached without validating that `remote` is actually a network remote. As a result, a user can supply a server filesystem path such as `$DATA_PATH/repos/secret.git` and cause the server to clone its own local bare repository into a new repo owned by the attacker.&lt;/p&gt;
&lt;p&gt;The relevant vulnerable flow is:
- [`pkg/ssh/cmd/import.go`](https://github.com/charmbracelet/soft-serve/b…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xgxp-f695-6vrp</guid>
    </item>
  </channel>
</rss>
