<?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>Mon, 05 Oct 2026 08:28:31 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-338356</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-338356</link>
      <description>EUVD-2026-338356</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-338356</guid>
    </item>
    <item>
      <title>fkie_cve-2026-49352</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-49352</link>
      <description>&lt;p&gt;9Router is an AI router &amp;amp; token saver. From 0.2.21 until 0.4.44, 9Router used the hardcoded fallback JWT secret 9router-default-secret-change-me in src/app/api/auth/login/route.js, src/middleware.js, and later src/lib/auth/dashboardSession.js, allowing attackers to forge an auth_token cookie when JWT_SECRET was unset. This issue is fixed in version 0.4.44&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;9Router is an AI router &amp;amp; token saver. From 0.2.21 until 0.4.44, 9Router used the hardcoded fallback JWT secret 9router-default-secret-change-me in src/app/api/auth/login/route.js, src/middleware.js, and later src/lib/auth/dashboardSession.js, allowing attackers to forge an auth_token cookie when JWT_SECRET was unset. This issue is fixed in version 0.4.44&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-49352</guid>
    </item>
    <item>
      <title>GHSA-jphh-m39h-6gwx — 9router's Hardcoded Default fallback JWT Secret  Allows Authentication Bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jphh-m39h-6gwx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: 9router&lt;/p&gt;
&lt;p&gt;### Summary
9router uses a publicly known hardcoded string `&amp;#34;9router-default-secret-change-me&amp;#34;` as the fallback of JWT secret for all Dashboard session JWTs when the `JWT_SECRET` environment variable is not set. Because this secret is committed in the public repository and unchanged across all releases, any unauthenticated remote attacker can forge a valid `auth_token` cookie and gain full access to dashboard and api (If JWT_SECRET is not set on server) . This vulnerable affected so many public 9router server
### Details
| Versions | File | Note |
|---|---|---|
| `&amp;gt;= 0.2.21, &amp;lt;= 0.4.30` | `src/app/api/auth/login/route.js` + `src/middleware.js` | Introduced in commit `23cfb19` |
| `&amp;gt;= 0.4.31, &amp;lt;= 0.4.41` | `src/lib/auth/dashboardSession.js` | Relocated by OIDC refactor `c3d91b0`, secret unchanged |&lt;/p&gt;
&lt;p&gt;Vulnerable Code&lt;/p&gt;
&lt;p&gt;**v0.2.21 – v0.4.30** — `src/app/api/auth/login/route.js` and `src/middleware.js`:&lt;/p&gt;
&lt;p&gt;```js
const SECRET = new TextEncoder().encode(
  process.env.JWT_SECRET || &amp;#34;9router-default-secret-change-me&amp;#34;
);
```&lt;/p&gt;
&lt;p&gt;**v0.4.31 – v0.4.41 (current)** — `src/lib/auth/dashboardSession.js` (centralized via OIDC refactor, commit `c3d91b0`):&lt;/p&gt;
&lt;p&gt;```js
const SECRET = new TextEncoder().encode(
  process.env.JWT_SECRET || &amp;#34;9router-default-secret-change-me&amp;#34;
);
```
The fallback string was introduced in commit `23cfb19` (2026-01-09) and has never been removed. The OIDC refactor in `c3d91b0` only relocated it to a shared module . This vulnerability has existed since 9router first introduced authen…&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
9router uses a publicly known hardcoded string `&amp;#34;9router-default-secret-change-me&amp;#34;` as the fallback of JWT secret for all Dashboard session JWTs when the `JWT_SECRET` environment variable is not set. Because this secret is committed in the public repository and unchanged across all releases, any unauthenticated remote attacker can forge a valid `auth_token` cookie and gain full access to dashboard and api (If JWT_SECRET is not set on server) . This vulnerable affected so many public 9router server
### Details
| Versions | File | Note |
|---|---|---|
| `&amp;gt;= 0.2.21, &amp;lt;= 0.4.30` | `src/app/api/auth/login/route.js` + `src/middleware.js` | Introduced in commit `23cfb19` |
| `&amp;gt;= 0.4.31, &amp;lt;= 0.4.41` | `src/lib/auth/dashboardSession.js` | Relocated by OIDC refactor `c3d91b0`, secret unchanged |&lt;/p&gt;
&lt;p&gt;Vulnerable Code&lt;/p&gt;
&lt;p&gt;**v0.2.21 – v0.4.30** — `src/app/api/auth/login/route.js` and `src/middleware.js`:&lt;/p&gt;
&lt;p&gt;```js
const SECRET = new TextEncoder().encode(
  process.env.JWT_SECRET || &amp;#34;9router-default-secret-change-me&amp;#34;
);
```&lt;/p&gt;
&lt;p&gt;**v0.4.31 – v0.4.41 (current)** — `src/lib/auth/dashboardSession.js` (centralized via OIDC refactor, commit `c3d91b0`):&lt;/p&gt;
&lt;p&gt;```js
const SECRET = new TextEncoder().encode(
  process.env.JWT_SECRET || &amp;#34;9router-default-secret-change-me&amp;#34;
);
```
The fallback string was introduced in commit `23cfb19` (2026-01-09) and has never been removed. The OIDC refactor in `c3d91b0` only relocated it to a shared module . This vulnerability has existed since 9router first introduced authen…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jphh-m39h-6gwx</guid>
    </item>
  </channel>
</rss>
