Security readout for executives and security teams
Plain-English summary
9Router had a hardcoded fallback JWT signing secret in affected versions. If an operator did not set JWT_SECRET, an unauthenticated attacker could create a valid session cookie and bypass authentication. The vendor says this is fixed in version 0.4.44.
Executive priority
Treat this as urgent for any deployed 9Router instance. Authentication bypass can lead to full confidentiality, integrity, and availability impact, but exposure depends on affected version and unset JWT_SECRET configuration.
Technical view
CVE-2026-49352 affects decolua 9Router versions from 0.2.21 before 0.4.44. The issue is CWE-798: a hardcoded fallback JWT secret used across authentication and middleware code when JWT_SECRET was unset, enabling forged auth_token cookies. CVSS is 9.8, network exploitable, low complexity, no privileges or user interaction required.
Likely exposure
Exposure is most likely in internet-accessible or internally reachable 9Router deployments running >=0.2.21 and <0.4.44 where JWT_SECRET was not explicitly configured.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The CVSS vector indicates remote unauthenticated exploitation is plausible if the vulnerable configuration exists.
Researcher notes
Evidence is consistent across the CVE data, GitHub advisory, fixing commit, and release tag. Do not assume broader product impact beyond decolua 9Router versions >=0.2.21 and <0.4.44. No cited source confirms exploitation in the wild.
Mitigation direction
- Upgrade 9Router to version 0.4.44 or later.
- Set a strong unique JWT_SECRET in every environment.
- Rotate JWT_SECRET after upgrade if the deployment may have been exposed.
- Invalidate existing dashboard sessions or auth_token cookies after remediation.
- Review the GitHub advisory and v0.4.44 release notes for vendor guidance.
Validation and detection
- Inventory all 9Router deployments and record running versions.
- Confirm affected deployments are not running versions >=0.2.21 and <0.4.44.
- Verify JWT_SECRET is explicitly set in production and staging environments.
- Check access logs for unusual dashboard or API activity before remediation.
- Confirm session invalidation occurred after secret rotation or upgrade.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-49352 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/decolua/9router/security/advisories/GHSA-jphh-m39h-6gwxCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/decolua/9router/commit/fe3ce25ae3cda48c0702c2d452e17f6ec214009dCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/decolua/9router/releases/tag/v0.4.44CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.