How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

361,925

Total vulnerabilities in the database

9router has unauthenticated CRUD on /api/providers and Full API Key Leak via /api/usage/stats — 9router

Exposure of Sensitive Information to an Unauthorized Actor

title: Unauthenticated CRUD on /api/providers and Full API Key Leak via /api/usage/stats product: 9Router version: <= 0.4.41 severity: critical cve_request: true

Summary

Multiple critical API security vulnerabilities were discovered in 9Router's Next.js dashboard. The /api/providers endpoints lack authentication entirely, allowing anyone to create, read, update, and delete provider connections. Additionally, /api/usage/stats exposes full plaintext API keys, and /api/usage/request-logs + /api/usage/request-details expose all users' request history and full conversation contents (including system prompts, user messages, assistant responses) without authentication.

Affected Endpoints

| Endpoint | Method | Issue | |---|---|---| | /api/providers | GET | Lists all provider connections with partial credentials, OAuth tokens, account IDs | | /api/providers/:id | GET | Read any single provider detail (IDOR) | | /api/providers | POST | Create arbitrary provider connections with attacker-controlled API keys | | /api/providers/:id | PUT | Modify any existing provider connection | | /api/providers/:id | DELETE | Delete any provider connection | | /api/usage/stats | GET | Exposes full plaintext API keys, per-account usage breakdown, cost data | | /api/usage/request-logs | GET | Exposes all users' request logs (model, tokens, cost, timestamp, provider) | | /api/usage/request-details/:id | GET | Exposes full conversation turns including system prompts, user messages, assistant responses | | /api/version | GET | Exposes current version info | | /api/models | GET | Exposes full model routing catalog | | /api/v1/models | GET | Exposes model list |

Impact

Critical: Provider CRUD without authentication

An attacker can:

Add a malicious provider — inject a provider that proxies through their server, capturing all prompts, responses, and API keys routed through 9Router
Modify existing providers — replace API keys with attacker-controlled ones, redirect traffic
Delete all providers — cause complete denial of service
Read all provider configurations — harvest partial credentials, GitHub Copilot OAuth tokens, Cloudflare account IDs, email addresses

Critical: Full API key leak via /api/usage/stats

The endpoint returns complete API key strings (e.g., sk-...) in plaintext alongside usage data per key, enabling unauthorized use of connected AI provider accounts.

Critical: Conversation history leak

/api/usage/request-details returns the full conversation history of other users' AI sessions, including system prompts, user messages, assistant responses, tool calls, and reasoning traces.

Steps to Reproduce

1. Unauthenticated read of all providers

curl -s https://&lt;host&gt;/api/providers

Returns all provider connections with email addresses, auth type, account IDs, and partial API key prefixes.

2. Create a provider without authentication

curl -X POST https://&lt;host&gt;/api/providers \
  -H &quot;Content-Type: application/json&quot; \
  -d &#039;{&quot;provider&quot;:&quot;openai&quot;,&quot;authType&quot;:&quot;apikey&quot;,&quot;name&quot;:&quot;rogue&quot;,&quot;apiKey&quot;:&quot;sk-attacker-controlled&quot;}&#039;

Returns the created connection object with a new UUID and isActive: true.

3. Modify an existing provider without authentication

curl -X PUT https://&lt;host&gt;/api/providers/&lt;existing-uuid&gt; \
  -H &quot;Content-Type: application/json&quot; \
  -d &#039;{&quot;name&quot;:&quot;modified&quot;,&quot;apiKey&quot;:&quot;sk-attacker-key&quot;}&#039;

Returns the updated connection object.

4. Delete a provider without authentication

curl -X DELETE https://&lt;host&gt;/api/providers/&lt;existing-uuid&gt;

Returns {"message":"Connection deleted successfully"}.

5. Read full usage stats with API keys

curl -s https://&lt;host&gt;/api/usage/stats

Returns full API key strings, per-account token/cost breakdown, recent requests.

6. Read request logs

curl -s &quot;https://&lt;host&gt;/api/usage/request-logs?page=1&amp;pageSize=50&quot;

Returns paginated request logs with timestamps, models, providers, user emails, token counts.

7. Read full conversation

curl -s https://&lt;host&gt;/api/usage/request-details/&lt;request-uuid&gt;

Returns complete conversation turns for that request.

8. Read version info

curl -s https://&lt;host&gt;/api/version

Returns {"currentVersion":"0.4.19","latestVersion":"0.4.45","hasUpdate":true}.

Root Cause

The Next.js API routes under src/app/api/* lack authentication middleware on several endpoints. Specifically:

/api/providers/* — No auth check before CRUD operations on provider connections stored in the database
/api/usage/stats — No auth check before returning aggregated usage data including full API keys
/api/usage/request-logs — No auth check before returning request history
/api/usage/request-details/:id — No auth check before returning full conversation contents

Suggested Fix

Add authentication middleware to all /api/providers/* routes (GET, POST, PUT, DELETE)
Add authentication middleware to all /api/usage/* routes
Never return full API key strings in any API response — return masked keys only
Never return GitHub Copilot tokens or similar OAuth secrets in API responses
Implement proper authorization checks so users can only access their own data
Add rate limiting to public endpoints

Resources

https://github.com/decolua/9router

Published: Jul 6, 2026
Updated: Jul 7, 2026
GHSA: GHSA-vjc7-jrh9-9j86
Severity: Critical
Exploit:
CISA KEV:

CVSS v3:

Severity: Critical
Score: 10
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

CWEs:

Affected Software
References

Software	From	Fixed in
9router	-	0.4.41.x

https://github.com/decolua/9router/security/advisories/GHSA-vjc7-jrh9-9j86

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.