<?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 20:59:06 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-338216</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-338216</link>
      <description>EUVD-2026-338216</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-338216</guid>
    </item>
    <item>
      <title>fkie_cve-2026-56679</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-56679</link>
      <description>&lt;p&gt;9Router is an AI router &amp;amp; token saver. Prior to 0.5.4, the PATCH /api/settings endpoint writes the entire request body to persistent settings without a field whitelist, allowing an authenticated user to set security-critical fields such as requireLogin and disable authentication for the whole application, exposing protected routes such as /api/keys and /api/providers to unauthenticated access. This issue is reported as fixed in version 0.5.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;9Router is an AI router &amp;amp; token saver. Prior to 0.5.4, the PATCH /api/settings endpoint writes the entire request body to persistent settings without a field whitelist, allowing an authenticated user to set security-critical fields such as requireLogin and disable authentication for the whole application, exposing protected routes such as /api/keys and /api/providers to unauthenticated access. This issue is reported as fixed in version 0.5.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-56679</guid>
    </item>
    <item>
      <title>GHSA-vmjq-hvgq-2wv4 — 9router: Mass assignment in PATCH /api/settings allows authenticated authorization downgrade</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vmjq-hvgq-2wv4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: 9router&lt;/p&gt;
&lt;p&gt;### Summary
The `PATCH /api/settings` endpoint writes the entire request body to persistent settings without a field whitelist. An authenticated user can set security-critical fields that are not meant to be modifiable here — notably `requireLogin`. Setting `requireLogin: false` disables authentication for the whole application, exposing all protected routes (e.g. `/api/keys`, `/api/providers`) to unauthenticated access.&lt;/p&gt;
&lt;p&gt;### Details
Root cause is unfiltered mass assignment (CWE-915):&lt;/p&gt;
&lt;p&gt;- `src/app/api/settings/route.js` (PATCH handler) parses the body and passes it to `updateSettings(body)`, with special handling only for `newPassword` and `oidcClientSecret`. All other fields pass through.
- `src/lib/db/repos/settingsRepo.js` — `updateSettings` does `next = { ...current, ...updates }`, so any key in the body overwrites stored settings, including `requireLogin`, `tunnelDashboardAccess`, `authMode`.
- `src/dashboardGuard.js` — `isAuthenticated` returns `true` whenever `settings.requireLogin === false`, bypassing auth on all protected routes.&lt;/p&gt;
&lt;p&gt;This is distinct from CVE-2026-5842 (CWE-285, pre-auth bypass on `/api`, patched in 0.3.75). This finding requires a valid authenticated session and abuses input handling, not missing authentication.&lt;/p&gt;
&lt;p&gt;### PoC
Instance on `localhost:20128`, default password `123456`.&lt;/p&gt;
&lt;p&gt;1. Authenticate, capture session:
   `POST /api/auth/login` body `{&amp;#34;password&amp;#34;:&amp;#34;123456&amp;#34;}` → `200 {&amp;#34;success&amp;#34;:true}`
2. Mass-assign with the authenticated session:
   `PATCH /api…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: 9router&lt;/p&gt;
&lt;p&gt;### Summary
The `PATCH /api/settings` endpoint writes the entire request body to persistent settings without a field whitelist. An authenticated user can set security-critical fields that are not meant to be modifiable here — notably `requireLogin`. Setting `requireLogin: false` disables authentication for the whole application, exposing all protected routes (e.g. `/api/keys`, `/api/providers`) to unauthenticated access.&lt;/p&gt;
&lt;p&gt;### Details
Root cause is unfiltered mass assignment (CWE-915):&lt;/p&gt;
&lt;p&gt;- `src/app/api/settings/route.js` (PATCH handler) parses the body and passes it to `updateSettings(body)`, with special handling only for `newPassword` and `oidcClientSecret`. All other fields pass through.
- `src/lib/db/repos/settingsRepo.js` — `updateSettings` does `next = { ...current, ...updates }`, so any key in the body overwrites stored settings, including `requireLogin`, `tunnelDashboardAccess`, `authMode`.
- `src/dashboardGuard.js` — `isAuthenticated` returns `true` whenever `settings.requireLogin === false`, bypassing auth on all protected routes.&lt;/p&gt;
&lt;p&gt;This is distinct from CVE-2026-5842 (CWE-285, pre-auth bypass on `/api`, patched in 0.3.75). This finding requires a valid authenticated session and abuses input handling, not missing authentication.&lt;/p&gt;
&lt;p&gt;### PoC
Instance on `localhost:20128`, default password `123456`.&lt;/p&gt;
&lt;p&gt;1. Authenticate, capture session:
   `POST /api/auth/login` body `{&amp;#34;password&amp;#34;:&amp;#34;123456&amp;#34;}` → `200 {&amp;#34;success&amp;#34;:true}`
2. Mass-assign with the authenticated session:
   `PATCH /api…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vmjq-hvgq-2wv4</guid>
    </item>
  </channel>
</rss>
