<?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>Tue, 06 Oct 2026 22:50:47 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-338927</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-338927</link>
      <description>EUVD-2026-338927</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-338927</guid>
    </item>
    <item>
      <title>fkie_cve-2026-45712</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-45712</link>
      <description>&lt;p&gt;Mailpit is an email testing tool and API for developers. Prior to version 1.30.0, the screenshot/print proxy (/proxy?data=…) maintains a package-level assets map[string]MessageAssets cache, but reads the map without holding assetsMutex while a long-running cleanup goroutine and (re-entrant) CSS-rewriting code path concurrently write to it under the lock. When the unsynchronized read coincides with a synchronized write, Go&amp;#39;s runtime raises fatal error: concurrent map read and map write — a runtime.throw that is not recoverable by http.Server&amp;#39;s handler-panic recover. The whole Mailpit process exits, taking the SMTP, POP3 and HTTP listeners down with it. Version 1.30.0 contains a patch.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Mailpit is an email testing tool and API for developers. Prior to version 1.30.0, the screenshot/print proxy (/proxy?data=…) maintains a package-level assets map[string]MessageAssets cache, but reads the map without holding assetsMutex while a long-running cleanup goroutine and (re-entrant) CSS-rewriting code path concurrently write to it under the lock. When the unsynchronized read coincides with a synchronized write, Go&amp;#39;s runtime raises fatal error: concurrent map read and map write — a runtime.throw that is not recoverable by http.Server&amp;#39;s handler-panic recover. The whole Mailpit process exits, taking the SMTP, POP3 and HTTP listeners down with it. Version 1.30.0 contains a patch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-45712</guid>
    </item>
    <item>
      <title>GHSA-w4vj-r5pg-3722 — Mailpit: Concurrent map read &amp; write in proxy CSS rewriter - remote unauth crash (fatal error: concurrent map read and…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w4vj-r5pg-3722</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/axllent/mailpit&lt;/p&gt;
&lt;p&gt;### Summary
The screenshot/print proxy (/proxy?data=…) maintains a package-level assets map[string]MessageAssets cache, but reads the map without holding assetsMutex while a long-running cleanup goroutine and (re-entrant) CSS-rewriting code path concurrently write to it under the lock. When the unsynchronized read coincides with a synchronized write, Go&amp;#39;s runtime raises fatal error: concurrent map read and map write — a runtime.throw that is not recoverable by http.Server&amp;#39;s handler-panic recover. The whole Mailpit process exits, taking the SMTP, POP3 and HTTP listeners down with it.&lt;/p&gt;
&lt;p&gt;### Details
A remote, unauthenticated attacker who can (1) reach /proxy and (2) plant any message with a stylesheet link in the inbox can crash Mailpit by issuing concurrent /proxy?data=… requests against the same message&amp;#39;s CSS URL. Mailpit&amp;#39;s defaults make both prerequisites trivial: the SMTP listener accepts mail anonymously, the HTTP listener accepts requests anonymously, and the cleanup goroutine fires every minute regardless of whether the map is being read.&lt;/p&gt;
&lt;p&gt;Affected code
[server/handlers/proxy.go:198-229](https://github.com/axllent/mailpit/blob/develop/server/handlers/proxy.go#L198-L229)
[server/handlers/proxy.go:52-66](https://github.com/axllent/mailpit/blob/develop/server/handlers/proxy.go#L52-L66)
[server/handlers/proxy.go:244-313](https://github.com/axllent/mailpit/blob/develop/server/handlers/proxy.go#L244-L313)&lt;/p&gt;
&lt;p&gt;Go&amp;#39;s map runtime sets a hashWriting flag at the start of any write op.…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/axllent/mailpit&lt;/p&gt;
&lt;p&gt;### Summary
The screenshot/print proxy (/proxy?data=…) maintains a package-level assets map[string]MessageAssets cache, but reads the map without holding assetsMutex while a long-running cleanup goroutine and (re-entrant) CSS-rewriting code path concurrently write to it under the lock. When the unsynchronized read coincides with a synchronized write, Go&amp;#39;s runtime raises fatal error: concurrent map read and map write — a runtime.throw that is not recoverable by http.Server&amp;#39;s handler-panic recover. The whole Mailpit process exits, taking the SMTP, POP3 and HTTP listeners down with it.&lt;/p&gt;
&lt;p&gt;### Details
A remote, unauthenticated attacker who can (1) reach /proxy and (2) plant any message with a stylesheet link in the inbox can crash Mailpit by issuing concurrent /proxy?data=… requests against the same message&amp;#39;s CSS URL. Mailpit&amp;#39;s defaults make both prerequisites trivial: the SMTP listener accepts mail anonymously, the HTTP listener accepts requests anonymously, and the cleanup goroutine fires every minute regardless of whether the map is being read.&lt;/p&gt;
&lt;p&gt;Affected code
[server/handlers/proxy.go:198-229](https://github.com/axllent/mailpit/blob/develop/server/handlers/proxy.go#L198-L229)
[server/handlers/proxy.go:52-66](https://github.com/axllent/mailpit/blob/develop/server/handlers/proxy.go#L52-L66)
[server/handlers/proxy.go:244-313](https://github.com/axllent/mailpit/blob/develop/server/handlers/proxy.go#L244-L313)&lt;/p&gt;
&lt;p&gt;Go&amp;#39;s map runtime sets a hashWriting flag at the start of any write op.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w4vj-r5pg-3722</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1558 — MailPit: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1558</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in MailPit ausnutzen, um Dateien zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in MailPit ausnutzen, um Dateien zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1558</guid>
    </item>
  </channel>
</rss>
