CVE-2026-49352

Deferred Deferred - Pending Action

Hardcoded JWT Secret in 9Router

Publication date: 2026-07-15

Last updated on: 2026-07-16

Assigner: GitHub, Inc.

Description

9Router is an AI router & 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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-15

Last Modified

2026-07-16

Generated

2026-08-06

AI Q&A

2026-07-16

EPSS Evaluated

2026-08-04

NVD

CVE-2026-49352

Affected Vendors & Products

Vendor	Product	Version / Range
9router	9router	From 0.2.21 (inc) to 0.4.44 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-798	The product contains hard-coded credentials, such as a password or cryptographic key.

Attack-Flow Graph

Executive Summary

The vulnerability is in 9Router versions 0.2.21 to 0.4.44 where a hardcoded fallback JWT secret (9router-default-secret-change-me) was used in multiple files. This allowed attackers to forge authentication tokens when the JWT_SECRET was not set, potentially gaining unauthorized access.

Detection Guidance

Check if your 9Router version is between 0.2.21 and 0.4.43. Inspect the files src/app/api/auth/login/route.js, src/middleware.js, and src/lib/auth/dashboardSession.js for the hardcoded JWT secret 9router-default-secret-change-me.

Impact Analysis

An attacker could forge an auth_token cookie to impersonate users, gain unauthorized access to the router's dashboard, and perform actions as if they were a legitimate user. This could lead to data theft, unauthorized configuration changes, or network compromise.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR (data protection) and HIPAA (health data privacy) by exposing personal or health information. Compliance requires fixing the issue and auditing affected systems.

Mitigation Strategies

Upgrade 9Router to version 0.4.44 or later to remove the hardcoded secret. If upgrading is not possible, ensure the JWT_SECRET environment variable is set to a strong, unique value to override the fallback secret.

Hi! I’m here to help you understand CVE-2026-49352. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70