CVE-2026-49352: 9router's Hardcoded Default fallback JWT Secret Allows Authentication Bypass
Affects 9routerSource GCVE Database
Not known to be exploited · CVSS 9.8 Critical : upgrade to 0.4.45 as a priority.
Data as of 26 Oct 2026, 11:07 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.4.45
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade 9router to 0.4.45.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm9router | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The recommended mitigation is to configure the JWT_SECRET environment variable with a strong, unique secret before starting 9router. The server should be modified to fail startup if JWT_SECRET is not set, preventing fallback to the insecure default. Alternatively, implement logic to generate and persist a random secret on first boot and never use the hardcoded fallback. Until this is done, any 9router instance without JWT_SECRET set remains vulnerable.
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