<?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 11:44:07 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-327251</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-327251</link>
      <description>EUVD-2026-327251</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-327251</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53520</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53520</link>
      <description>&lt;p&gt;Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&amp;amp;M tool. From version 2.0.14 to before version 2.1.0, authenticated users can claim the dashboard Host through NAT and preempt all dashboard routing. This issue has been patched in version 2.1.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&amp;amp;M tool. From version 2.0.14 to before version 2.1.0, authenticated users can claim the dashboard Host through NAT and preempt all dashboard routing. This issue has been patched in version 2.1.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53520</guid>
    </item>
    <item>
      <title>GHSA-x6fg-52vr-hj4w — Nezha Monitoring: Authenticated users can claim the dashboard Host through NAT and preempt all dashboard routing</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x6fg-52vr-hj4w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/nezhahq/nezha&lt;/p&gt;
&lt;p&gt;### Summary
An authenticated non-admin user who owns any server can create or update a NAT profile whose `domain` is equal to the dashboard&amp;#39;s own HTTP Host (for example, `dashboard.example:8008`). The dashboard&amp;#39;s top-level HTTP/gRPC multiplexer checks `NATShared.GetNATConfigByDomain(r.Host)` before dispatching requests to the dashboard API, frontend, or gRPC handler, so a member-controlled NAT profile for the dashboard Host takes precedence over the real dashboard.&lt;/p&gt;
&lt;p&gt;A disabled claimed NAT profile blocks matching dashboard requests before they reach the dashboard handler. An enabled claimed NAT profile routes matching requests into `ServeNAT`, which sends a NAT task to the member&amp;#39;s selected agent and wraps the original HTTP request into the NAT IO stream. This allows a low-privileged dashboard user to take over routing for a global host name that should be reserved for the dashboard operator.&lt;/p&gt;
&lt;p&gt;Tested locally against commit `8b5e382fe217107c7b777ea9c6b4bc3d2e156202` of `github.com/nezhahq/nezha`.&lt;/p&gt;
&lt;p&gt;### Details
The NAT management API is exposed to any authenticated user, not just administrators: `auth.POST(&amp;#34;/nat&amp;#34;, commonHandler(createNAT))` and `auth.PATCH(&amp;#34;/nat/:id&amp;#34;, commonHandler(updateNAT))` are registered in `cmd/dashboard/controller/controller.go:147-150`.&lt;/p&gt;
&lt;p&gt;`createNAT` accepts the request body into `model.NATForm`, verifies only that the selected server exists and `server.HasPermission(c)` succeeds, then stores the caller-controlled `nf.Domain` directly into `n.Domain` and…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/nezhahq/nezha&lt;/p&gt;
&lt;p&gt;### Summary
An authenticated non-admin user who owns any server can create or update a NAT profile whose `domain` is equal to the dashboard&amp;#39;s own HTTP Host (for example, `dashboard.example:8008`). The dashboard&amp;#39;s top-level HTTP/gRPC multiplexer checks `NATShared.GetNATConfigByDomain(r.Host)` before dispatching requests to the dashboard API, frontend, or gRPC handler, so a member-controlled NAT profile for the dashboard Host takes precedence over the real dashboard.&lt;/p&gt;
&lt;p&gt;A disabled claimed NAT profile blocks matching dashboard requests before they reach the dashboard handler. An enabled claimed NAT profile routes matching requests into `ServeNAT`, which sends a NAT task to the member&amp;#39;s selected agent and wraps the original HTTP request into the NAT IO stream. This allows a low-privileged dashboard user to take over routing for a global host name that should be reserved for the dashboard operator.&lt;/p&gt;
&lt;p&gt;Tested locally against commit `8b5e382fe217107c7b777ea9c6b4bc3d2e156202` of `github.com/nezhahq/nezha`.&lt;/p&gt;
&lt;p&gt;### Details
The NAT management API is exposed to any authenticated user, not just administrators: `auth.POST(&amp;#34;/nat&amp;#34;, commonHandler(createNAT))` and `auth.PATCH(&amp;#34;/nat/:id&amp;#34;, commonHandler(updateNAT))` are registered in `cmd/dashboard/controller/controller.go:147-150`.&lt;/p&gt;
&lt;p&gt;`createNAT` accepts the request body into `model.NATForm`, verifies only that the selected server exists and `server.HasPermission(c)` succeeds, then stores the caller-controlled `nf.Domain` directly into `n.Domain` and…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x6fg-52vr-hj4w</guid>
    </item>
  </channel>
</rss>
