<?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 15:54:57 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-291052</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-291052</link>
      <description>EUVD-2026-291052</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-291052</guid>
    </item>
    <item>
      <title>fkie_cve-2026-40189</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-40189</link>
      <description>&lt;p&gt;goshs is a SimpleHTTPServer written in Go. Prior to 2.0.0-beta.4, goshs enforces the documented per-folder .goshs ACL/basic-auth mechanism for directory listings and file reads, but it does not enforce the same authorization checks for state-changing routes. An unauthenticated attacker can upload files with PUT, upload files with multipart POST /upload, create directories with ?mkdir, and delete files with ?delete inside a .goshs-protected directory. By deleting the .goshs file itself, the attacker can remove the folder&amp;#39;s auth policy and then access previously protected content without credentials. This results in a critical authorization bypass affecting confidentiality, integrity, and availability. This vulnerability is fixed in 2.0.0-beta.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;goshs is a SimpleHTTPServer written in Go. Prior to 2.0.0-beta.4, goshs enforces the documented per-folder .goshs ACL/basic-auth mechanism for directory listings and file reads, but it does not enforce the same authorization checks for state-changing routes. An unauthenticated attacker can upload files with PUT, upload files with multipart POST /upload, create directories with ?mkdir, and delete files with ?delete inside a .goshs-protected directory. By deleting the .goshs file itself, the attacker can remove the folder&amp;#39;s auth policy and then access previously protected content without credentials. This results in a critical authorization bypass affecting confidentiality, integrity, and availability. This vulnerability is fixed in 2.0.0-beta.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-40189</guid>
    </item>
    <item>
      <title>GHSA-wvhv-qcqf-f3cx — goshs has a file-based ACL authorization bypass in goshs state-changing routes</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wvhv-qcqf-f3cx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/patrickhener/goshs&lt;/p&gt;
&lt;p&gt;### Summary
goshs enforces the documented per-folder `.goshs` ACL/basic-auth mechanism for directory listings and file reads, but it does not enforce the same authorization checks for state-changing routes. An unauthenticated attacker can upload files with `PUT`, upload files with multipart `POST /upload`, create directories with `?mkdir`, and delete files with `?delete` inside a `.goshs`-protected directory. By deleting the `.goshs` file itself, the attacker can remove the folder&amp;#39;s auth policy and then access previously protected content without credentials. This results in a critical authorization bypass affecting confidentiality, integrity, and availability.&lt;/p&gt;
&lt;p&gt;### Details
The project README explicitly documents file-based ACLs as a security feature:&lt;/p&gt;
&lt;p&gt;- `README.md:59` - &amp;#34;You can place a .goshs in any folder to apply custom ACLs&amp;#34;
- `README.md:61` - &amp;#34;You can apply custom basic auth per folder&amp;#34;&lt;/p&gt;
&lt;p&gt;The read/list path correctly enforces `.goshs`:&lt;/p&gt;
&lt;p&gt;- `httpserver/filebased.go:10-49` loads `.goshs`
- `httpserver/handler.go:68-91` calls `findSpecialFile()` for directories
- `httpserver/handler.go:94-101` calls `findSpecialFile()` for files
- `httpserver/handler.go:285-305` applies custom auth
- `httpserver/handler.go:545-565` enforces folder auth during directory rendering
- `httpserver/handler.go:590-630` enforces file auth and blocked entries during file serving&lt;/p&gt;
&lt;p&gt;However, the state-changing routes bypass this logic entirely:&lt;/p&gt;
&lt;p&gt;- `httpserver/server.go:94-100` routes multipart `POST /.…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/patrickhener/goshs&lt;/p&gt;
&lt;p&gt;### Summary
goshs enforces the documented per-folder `.goshs` ACL/basic-auth mechanism for directory listings and file reads, but it does not enforce the same authorization checks for state-changing routes. An unauthenticated attacker can upload files with `PUT`, upload files with multipart `POST /upload`, create directories with `?mkdir`, and delete files with `?delete` inside a `.goshs`-protected directory. By deleting the `.goshs` file itself, the attacker can remove the folder&amp;#39;s auth policy and then access previously protected content without credentials. This results in a critical authorization bypass affecting confidentiality, integrity, and availability.&lt;/p&gt;
&lt;p&gt;### Details
The project README explicitly documents file-based ACLs as a security feature:&lt;/p&gt;
&lt;p&gt;- `README.md:59` - &amp;#34;You can place a .goshs in any folder to apply custom ACLs&amp;#34;
- `README.md:61` - &amp;#34;You can apply custom basic auth per folder&amp;#34;&lt;/p&gt;
&lt;p&gt;The read/list path correctly enforces `.goshs`:&lt;/p&gt;
&lt;p&gt;- `httpserver/filebased.go:10-49` loads `.goshs`
- `httpserver/handler.go:68-91` calls `findSpecialFile()` for directories
- `httpserver/handler.go:94-101` calls `findSpecialFile()` for files
- `httpserver/handler.go:285-305` applies custom auth
- `httpserver/handler.go:545-565` enforces folder auth during directory rendering
- `httpserver/handler.go:590-630` enforces file auth and blocked entries during file serving&lt;/p&gt;
&lt;p&gt;However, the state-changing routes bypass this logic entirely:&lt;/p&gt;
&lt;p&gt;- `httpserver/server.go:94-100` routes multipart `POST /.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wvhv-qcqf-f3cx</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10542-1 — goshs-2.0.0-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10542-1</link>
      <description>&lt;p&gt;goshs-2.0.0-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;goshs-2.0.0-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10542-1</guid>
    </item>
  </channel>
</rss>
