CVE-2026-49352: decolua 9Router authentication bypass via hardcoded JWT secret

CVE-2026-49352 · Severity: critical · CVSS 9.8 · Published 2026-07-15

9Router, an AI routing and token management tool, contains a security flaw where it uses a publicly known, hardcoded password to secure user sessions if a custom secret is not configured by the administrator. This allows an attacker to easily create their own login credentials and gain full administrative access to the router's dashboard. Once inside, an attacker can steal sensitive API keys, modify system settings, or shut down the service entirely.

Technologies: 9router (npm). Vendors: npm.

Quick answers

Is CVE-2026-49352 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-49352 being exploited in the wild.
How severe is CVE-2026-49352?
Critical severity, with a CVSS score of 9.8, published 15 July 2026.
Which products and versions are affected?
9router (npm) >= 0.2.21, <= 0.4.41, SEMVER:introduced=0.2.21,fixed=0.4.45.
Is there a fix for CVE-2026-49352?
Yes. 9router (npm): upgrade to 0.4.45 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-49352 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-49352?
Check whether you run 9router (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • 9router (npm): upgrade to 0.4.45 or later
    npm install 9router@0.4.45

Technical details

9Router (versions 0.2.21 through 0.4.43) implements a hardcoded fallback string ('9router-default-secret-change-me') for signing JSON Web Tokens (JWT) used in dashboard sessions. This occurs in src/app/api/auth/login/route.js and src/middleware.js (and later src/lib/auth/dashboardSession.js) whenever the JWT_SECRET environment variable is not explicitly defined by the user. A remote, unauthenticated attacker can use this publicly known secret to sign a forged 'auth_token' cookie. By presenting this forged cookie, the attacker achieves a complete authentication bypass, granting them full access to the dashboard and API, including the ability to extract stored API keys and database credentials. The issue is resolved in version 0.4.44 by removing the fallback and requiring a user-defined secret.

Affected products

  • decolua 9Router 0.2.21 to 0.4.43

Identifiers

  • CVE-2026-49352
  • GHSA-jphh-m39h-6gwx

Timeline

  • 2026-01-09: other: Vulnerability introduced in commit 23cfb19
  • 2026-05-15: patched: Version 0.4.44 released with fix
  • 2026-05-31: advisory: GitHub Security Advisory published
  • 2026-07-15: disclosed: CVE-2026-49352 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.