<?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>Wed, 07 Oct 2026 02:42:26 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-308576</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-308576</link>
      <description>EUVD-2026-308576</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-308576</guid>
    </item>
    <item>
      <title>fkie_cve-2026-42091</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-42091</link>
      <description>&lt;p&gt;goshs is a SimpleHTTPServer written in Go. Prior to version 2.0.2, the PUT upload handler (httpserver/updown.go) lacks the CSRF token validation that was added to the POST upload handler during the CVE-2026-40883 fix. Combined with the unconditional Access-Control-Allow-Origin: * on the OPTIONS preflight handler (httpserver/server.go), any website can write arbitrary files to a goshs instance through the victim&amp;#39;s browser — bypassing network isolation (e.g. localhost, internal network). This issue has been patched in version 2.0.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;goshs is a SimpleHTTPServer written in Go. Prior to version 2.0.2, the PUT upload handler (httpserver/updown.go) lacks the CSRF token validation that was added to the POST upload handler during the CVE-2026-40883 fix. Combined with the unconditional Access-Control-Allow-Origin: * on the OPTIONS preflight handler (httpserver/server.go), any website can write arbitrary files to a goshs instance through the victim&amp;#39;s browser — bypassing network isolation (e.g. localhost, internal network). This issue has been patched in version 2.0.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-42091</guid>
    </item>
    <item>
      <title>GHSA-rhf7-wvw3-vjvm — goshs has Cross-Origin Arbitrary File Write via Missing CSRF on PUT and Wildcard CORS</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rhf7-wvw3-vjvm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/patrickhener/goshs/v2, Go: github.com/patrickhener/goshs&lt;/p&gt;
&lt;p&gt;### Summary
The PUT upload handler (`httpserver/updown.go`) lacks the CSRF token validation that was added to the POST upload handler during the GHSA-jrq5-hg6x-j6g3 fix. Combined with the unconditional `Access-Control-Allow-Origin: *` on the OPTIONS preflight handler (`httpserver/server.go`), any website can write arbitrary files to a goshs instance through the victim&amp;#39;s browser — bypassing network isolation (e.g. localhost, internal network).&lt;/p&gt;
&lt;p&gt;### Details
**Root Cause 1 — Missing CSRF on PUT** (`httpserver/updown.go:19`)&lt;/p&gt;
&lt;p&gt;When GHSA-jrq5-hg6x-j6g3 was fixed (commit `e3c3d37`), `checkCSRF()` was added to the POST `upload()` function (line 78) but not to the PUT `put()` function directly above it in the same file. This means PUT requests are accepted without any CSRF token.&lt;/p&gt;
&lt;p&gt;```go
// POST — protected 
func (fs *FileServer) upload(w http.ResponseWriter, req *http.Request) {
    if !fs.checkCSRF(w, req) { return }
    // ...
}&lt;/p&gt;
&lt;p&gt;// PUT — unprotected 
func (fs *FileServer) put(w http.ResponseWriter, req *http.Request) {
    // No checkCSRF call
    // ...
}
```&lt;/p&gt;
&lt;p&gt;**Root Cause 2 — Wildcard CORS** (`httpserver/server.go:126`)&lt;/p&gt;
&lt;p&gt;The OPTIONS handler unconditionally returns permissive CORS headers:&lt;/p&gt;
&lt;p&gt;```go
w.Header().Set(&amp;#34;Access-Control-Allow-Origin&amp;#34;, &amp;#34;*&amp;#34;)
w.Header().Set(&amp;#34;Access-Control-Allow-Methods&amp;#34;, &amp;#34;POST, PUT, OPTIONS&amp;#34;)
w.Header().Set(&amp;#34;Access-Control-Allow-Headers&amp;#34;, &amp;#34;Content-Type, Authorization&amp;#34;)
```&lt;/p&gt;
&lt;p&gt;This allows any website&amp;#39;s JavaScript to pass the browser&amp;#39;s CORS preflight check and s…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/patrickhener/goshs/v2, Go: github.com/patrickhener/goshs&lt;/p&gt;
&lt;p&gt;### Summary
The PUT upload handler (`httpserver/updown.go`) lacks the CSRF token validation that was added to the POST upload handler during the GHSA-jrq5-hg6x-j6g3 fix. Combined with the unconditional `Access-Control-Allow-Origin: *` on the OPTIONS preflight handler (`httpserver/server.go`), any website can write arbitrary files to a goshs instance through the victim&amp;#39;s browser — bypassing network isolation (e.g. localhost, internal network).&lt;/p&gt;
&lt;p&gt;### Details
**Root Cause 1 — Missing CSRF on PUT** (`httpserver/updown.go:19`)&lt;/p&gt;
&lt;p&gt;When GHSA-jrq5-hg6x-j6g3 was fixed (commit `e3c3d37`), `checkCSRF()` was added to the POST `upload()` function (line 78) but not to the PUT `put()` function directly above it in the same file. This means PUT requests are accepted without any CSRF token.&lt;/p&gt;
&lt;p&gt;```go
// POST — protected 
func (fs *FileServer) upload(w http.ResponseWriter, req *http.Request) {
    if !fs.checkCSRF(w, req) { return }
    // ...
}&lt;/p&gt;
&lt;p&gt;// PUT — unprotected 
func (fs *FileServer) put(w http.ResponseWriter, req *http.Request) {
    // No checkCSRF call
    // ...
}
```&lt;/p&gt;
&lt;p&gt;**Root Cause 2 — Wildcard CORS** (`httpserver/server.go:126`)&lt;/p&gt;
&lt;p&gt;The OPTIONS handler unconditionally returns permissive CORS headers:&lt;/p&gt;
&lt;p&gt;```go
w.Header().Set(&amp;#34;Access-Control-Allow-Origin&amp;#34;, &amp;#34;*&amp;#34;)
w.Header().Set(&amp;#34;Access-Control-Allow-Methods&amp;#34;, &amp;#34;POST, PUT, OPTIONS&amp;#34;)
w.Header().Set(&amp;#34;Access-Control-Allow-Headers&amp;#34;, &amp;#34;Content-Type, Authorization&amp;#34;)
```&lt;/p&gt;
&lt;p&gt;This allows any website&amp;#39;s JavaScript to pass the browser&amp;#39;s CORS preflight check and s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rhf7-wvw3-vjvm</guid>
    </item>
  </channel>
</rss>
