<?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, 12 Oct 2026 07:40:25 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-335681</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-335681</link>
      <description>EUVD-2026-335681</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-335681</guid>
    </item>
    <item>
      <title>fkie_cve-2026-55638</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-55638</link>
      <description>&lt;p&gt;9Router is an AI router &amp;amp; token saver. Prior to 0.5.2, 9router protects /v1, /v1beta, /api/v1, and /api/v1beta in src/dashboardGuard.js but omits /codex before next.config.mjs rewrites /codex/* to /api/v1/responses. A remote unauthenticated attacker can send requests to /codex/* to bypass the API-key gate and cause the server to make upstream provider calls using operator-stored LLM provider credentials. This issue is fixed in version 0.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;9Router is an AI router &amp;amp; token saver. Prior to 0.5.2, 9router protects /v1, /v1beta, /api/v1, and /api/v1beta in src/dashboardGuard.js but omits /codex before next.config.mjs rewrites /codex/* to /api/v1/responses. A remote unauthenticated attacker can send requests to /codex/* to bypass the API-key gate and cause the server to make upstream provider calls using operator-stored LLM provider credentials. This issue is fixed in version 0.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-55638</guid>
    </item>
    <item>
      <title>GHSA-8gmq-j984-vp4r — 9router: Unauthenticated LLM proxy access via /codex rewrite authorization bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8gmq-j984-vp4r</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: 9router&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;9router exposes an OpenAI/Anthropic-compatible LLM proxy. Remote access to this proxy is intended to be protected by an API-key check in the Next.js middleware.&lt;/p&gt;
&lt;p&gt;However, 9router also defines a rewrite that maps `/codex/*` to the backend LLM endpoint `/api/v1/responses`. The middleware authorization decision is made on the incoming request path before the rewrite is applied. Because `/codex` is not included in the middleware&amp;#39;s protected LLM API prefix list, requests to `/codex/*` bypass the API-key gate and are later rewritten to the same backend used by `/api/v1/responses`.&lt;/p&gt;
&lt;p&gt;As a result, an unauthenticated remote attacker can access the LLM proxy through `/codex/*` and cause the server to make upstream provider calls using the operator-stored LLM provider credentials.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;| Component                     | File                                | Note                                                                      |
| ----------------------------- | ----------------------------------- | ------------------------------------------------------------------------- |
| Middleware authorization gate | `src/dashboardGuard.js`             | Protects `/v1`, `/v1beta`, `/api/v1`, and `/api/v1beta`, but not `/codex` |
| Rewrite configuration         | `next.config.mjs`                   | Rewrites `/codex/:path*` to `/api/v1/responses`                           |
| LLM backend route             | `src/app/api/v1/responses/route.js` | Dispatches rewritten requests…&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&lt;/p&gt;
&lt;p&gt;9router exposes an OpenAI/Anthropic-compatible LLM proxy. Remote access to this proxy is intended to be protected by an API-key check in the Next.js middleware.&lt;/p&gt;
&lt;p&gt;However, 9router also defines a rewrite that maps `/codex/*` to the backend LLM endpoint `/api/v1/responses`. The middleware authorization decision is made on the incoming request path before the rewrite is applied. Because `/codex` is not included in the middleware&amp;#39;s protected LLM API prefix list, requests to `/codex/*` bypass the API-key gate and are later rewritten to the same backend used by `/api/v1/responses`.&lt;/p&gt;
&lt;p&gt;As a result, an unauthenticated remote attacker can access the LLM proxy through `/codex/*` and cause the server to make upstream provider calls using the operator-stored LLM provider credentials.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;| Component                     | File                                | Note                                                                      |
| ----------------------------- | ----------------------------------- | ------------------------------------------------------------------------- |
| Middleware authorization gate | `src/dashboardGuard.js`             | Protects `/v1`, `/v1beta`, `/api/v1`, and `/api/v1beta`, but not `/codex` |
| Rewrite configuration         | `next.config.mjs`                   | Rewrites `/codex/:path*` to `/api/v1/responses`                           |
| LLM backend route             | `src/app/api/v1/responses/route.js` | Dispatches rewritten requests…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8gmq-j984-vp4r</guid>
    </item>
  </channel>
</rss>
