https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 17:49:28 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-56678 <p>9Router is an AI router &amp; token saver. Prior to 0.5.6, the Kiro API-key validation endpoint POST /api/oauth/kiro/api-key builds an upstream URL using a user-controlled region value, allowing an authenticated attacker to supply a crafted region such as kiro-canary.local:8443# and cause 9Router to send the Kiro validation request to an attacker-controlled host while forwarding the submitted Kiro API key as an Authorization header. This issue is fixed in version 0.5.6.</p> <p>9Router is an AI router &amp; token saver. Prior to 0.5.6, the Kiro API-key validation endpoint POST /api/oauth/kiro/api-key builds an upstream URL using a user-controlled region value, allowing an authenticated attacker to supply a crafted region such as kiro-canary.local:8443# and cause 9Router to send the Kiro validation request to an attacker-controlled host while forwarding the submitted Kiro API key as an Authorization header. This issue is fixed in version 0.5.6.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-56678 https://vulnerability.circl.lu/vuln/ghsa-6mwv-4mrm-5p3m <p><strong>Affected:</strong> npm: 9router</p> <p>### Summary</p> <p>The Kiro API-key validation endpoint builds an upstream URL using a user-controlled `region` value. By supplying a crafted region such as `kiro-canary.local:8443#`, an authenticated attacker can cause 9router to send the Kiro validation request to an attacker-controlled host under the constructed `codewhisperer.&lt;region&gt;` hostname. The request forwards the submitted Kiro API key as an `Authorization: Bearer` header.</p> <p>### Details</p> <p>- **Affected version / commit:** 9router v0.5.2 @ `5da508a`. - **Endpoint:** `POST /api/oauth/kiro/api-key`. - **Correct runtime payload:** `region: &#34;kiro-canary.local:8443#&#34;`. - Do **not** use the old `@host#` payload (`region: &#34;@kiro-canary.local:8443#&#34;`); it is blocked by Node/undici `fetch()` because it creates URL credentials (`&#34;Request cannot be constructed from a URL that includes credentials&#34;`). - **Constructed upstream host becomes:** `codewhisperer.kiro-canary.local:8443` (the `#` turns the trailing `.amazonaws.com` into a URL fragment). - HTTPS canary captured: `Authorization: Bearer DUMMY_KIRO_API_KEY_FOR_LOCAL_REPRO`. - TLS verification was **not** globally disabled; the reproduction uses a local CA via `NODE_EXTRA_CA_CERTS`. - The no-auth control returns 401, so this standalone issue is **authenticated**. - `SameSite=Lax` on the session cookie prevents cross-site POST cookie delivery, so do **not** claim drive-by CSRF unless another same-site / auth-bypass primitive is chained.</p> <p>**Root cause.** The route reads `…</p> <p><strong>Affected:</strong> npm: 9router</p> <p>### Summary</p> <p>The Kiro API-key validation endpoint builds an upstream URL using a user-controlled `region` value. By supplying a crafted region such as `kiro-canary.local:8443#`, an authenticated attacker can cause 9router to send the Kiro validation request to an attacker-controlled host under the constructed `codewhisperer.&lt;region&gt;` hostname. The request forwards the submitted Kiro API key as an `Authorization: Bearer` header.</p> <p>### Details</p> <p>- **Affected version / commit:** 9router v0.5.2 @ `5da508a`. - **Endpoint:** `POST /api/oauth/kiro/api-key`. - **Correct runtime payload:** `region: &#34;kiro-canary.local:8443#&#34;`. - Do **not** use the old `@host#` payload (`region: &#34;@kiro-canary.local:8443#&#34;`); it is blocked by Node/undici `fetch()` because it creates URL credentials (`&#34;Request cannot be constructed from a URL that includes credentials&#34;`). - **Constructed upstream host becomes:** `codewhisperer.kiro-canary.local:8443` (the `#` turns the trailing `.amazonaws.com` into a URL fragment). - HTTPS canary captured: `Authorization: Bearer DUMMY_KIRO_API_KEY_FOR_LOCAL_REPRO`. - TLS verification was **not** globally disabled; the reproduction uses a local CA via `NODE_EXTRA_CA_CERTS`. - The no-auth control returns 401, so this standalone issue is **authenticated**. - `SameSite=Lax` on the session cookie prevents cross-site POST cookie delivery, so do **not** claim drive-by CSRF unless another same-site / auth-bypass primitive is chained.</p> <p>**Root cause.** The route reads `…</p> https://vulnerability.circl.lu/vuln/ghsa-6mwv-4mrm-5p3m