Security readout for executives and security teams
Plain-English summary
9Router versions 0.4.30 through before 0.4.37 left sensitive plugin and MCP API routes unauthenticated. A remote attacker could register a custom plugin and use the MCP bridge to execute commands. Because exploitation needs no login or user interaction, the business risk is severe where affected instances are reachable.
Executive priority
Treat this as an urgent remediation item for any reachable 9Router deployment. A vulnerable instance could allow direct server command execution without credentials, so patching and exposure reduction should take priority over routine maintenance.
Technical view
The issue combines missing authentication on /api/cli-tools/* and /api/mcp/* with command execution through the MCP bridge. Sources identify CWE-306 and CWE-78, CVSS 10.0, and affected decolua 9router versions >=0.4.30 and <0.4.37. The reported fix is 0.4.37.
Likely exposure
Exposure is most likely for organizations running 9Router 0.4.30 to before 0.4.37, especially if the service or its API routes are reachable from untrusted networks.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates remote, unauthenticated, low-complexity exploitation with no user interaction, but exploit availability is not established by the provided sources.
Researcher notes
Evidence is strong for affected versions, vulnerable route classes, weakness types, and fixed version. The bundle does not provide exploit code, observed exploitation, affected hosted services, or detailed post-fix behavior, so validation should remain source-grounded and non-invasive.
Mitigation direction
- Upgrade 9Router to version 0.4.37 or later.
- Restrict access to /api/cli-tools/* and /api/mcp/* from untrusted networks.
- Review vendor advisory and commit notes for deployment-specific guidance.
- Audit configured customPlugins and remove unrecognized entries.
- Review logs for suspicious access to the affected API routes.
Validation and detection
- Inventory all 9Router deployments and record running versions.
- Confirm no instance runs >=0.4.30 and <0.4.37.
- Verify affected API routes require authentication after remediation.
- Check logs for unauthenticated requests to MCP or CLI-tools routes.
- Review custom plugin configuration for unauthorized changes.
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-306: 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 lookupCWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-46339 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
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:C/C:H/I:H/A:H3.96GitHub_MVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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-fhh6-4qxv-rpqjCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/decolua/9router/commit/992f4db4a0d858bcc86b4786f2abab117a6ccdf8CVE 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.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.