<?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 15:15:14 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-327285</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-327285</link>
      <description>EUVD-2026-327285</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-327285</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53521</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53521</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, PATCH /server/{id} accepts and persists nonexistent ddns_profiles IDs for a member-owned server. If another user later creates a DDNS profile with one of those IDs, the DDNS worker resolves the stored ID and dispatches an update using the other user&amp;#39;s DDNS profile configuration in the context of the attacker&amp;#39;s server. 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, PATCH /server/{id} accepts and persists nonexistent ddns_profiles IDs for a member-owned server. If another user later creates a DDNS profile with one of those IDs, the DDNS worker resolves the stored ID and dispatches an update using the other user&amp;#39;s DDNS profile configuration in the context of the attacker&amp;#39;s server. 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-53521</guid>
    </item>
    <item>
      <title>GHSA-39g2-8x68-pmx8 — Nezha Monitoring: Stored future DDNS profile ID allows unauthorized use of another user's DDNS profile context</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-39g2-8x68-pmx8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/nezhahq/nezha&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`PATCH /server/{id}` accepts and persists nonexistent `ddns_profiles` IDs for a member-owned server. If another user later creates a DDNS profile with one of those IDs, the DDNS worker resolves the stored ID and dispatches an update using the other user&amp;#39;s DDNS profile configuration in the context of the attacker&amp;#39;s server.&lt;/p&gt;
&lt;p&gt;This is a second-order authorization bypass: direct binding to an existing foreign DDNS profile is correctly denied, but an unresolved future ID can be stored first and later becomes a live cross-user reference.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;Confirmed on:&lt;/p&gt;
&lt;p&gt;- Nezha `v2.0.14`
- Commit: `8b5e382fe217107c7b777ea9c6b4bc3d2e156202`&lt;/p&gt;
&lt;p&gt;The exact affected version range was not determined.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;A normal member who owns a server can prebind one or more future DDNS profile IDs to that server. If another user later creates a DDNS profile with a matching ID, the dashboard DDNS worker can use the victim&amp;#39;s DDNS profile/provider configuration for the attacker&amp;#39;s server.&lt;/p&gt;
&lt;p&gt;In the validated worker path, the dispatched DDNS update combines:&lt;/p&gt;
&lt;p&gt;- the victim DDNS profile ID and owner
- the victim profile&amp;#39;s provider type
- victim profile fields such as domains, access ID, access secret, and retry policy
- attacker server context, including the attacker&amp;#39;s server ID, owner, IPv4 address, and override DDNS domains&lt;/p&gt;
&lt;p&gt;This can result in unauthorized DDNS update attempts using another user&amp;#39;s DDNS profile context. The attacker does not need permission to bind the victim profile a…&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&lt;/p&gt;
&lt;p&gt;`PATCH /server/{id}` accepts and persists nonexistent `ddns_profiles` IDs for a member-owned server. If another user later creates a DDNS profile with one of those IDs, the DDNS worker resolves the stored ID and dispatches an update using the other user&amp;#39;s DDNS profile configuration in the context of the attacker&amp;#39;s server.&lt;/p&gt;
&lt;p&gt;This is a second-order authorization bypass: direct binding to an existing foreign DDNS profile is correctly denied, but an unresolved future ID can be stored first and later becomes a live cross-user reference.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;Confirmed on:&lt;/p&gt;
&lt;p&gt;- Nezha `v2.0.14`
- Commit: `8b5e382fe217107c7b777ea9c6b4bc3d2e156202`&lt;/p&gt;
&lt;p&gt;The exact affected version range was not determined.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;A normal member who owns a server can prebind one or more future DDNS profile IDs to that server. If another user later creates a DDNS profile with a matching ID, the dashboard DDNS worker can use the victim&amp;#39;s DDNS profile/provider configuration for the attacker&amp;#39;s server.&lt;/p&gt;
&lt;p&gt;In the validated worker path, the dispatched DDNS update combines:&lt;/p&gt;
&lt;p&gt;- the victim DDNS profile ID and owner
- the victim profile&amp;#39;s provider type
- victim profile fields such as domains, access ID, access secret, and retry policy
- attacker server context, including the attacker&amp;#39;s server ID, owner, IPv4 address, and override DDNS domains&lt;/p&gt;
&lt;p&gt;This can result in unauthorized DDNS update attempts using another user&amp;#39;s DDNS profile context. The attacker does not need permission to bind the victim profile a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-39g2-8x68-pmx8</guid>
    </item>
  </channel>
</rss>
