WeKnora has Remote Code Execution (RCE) via Command Injection in MCP Stdio Configuration Validation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2026-30861: 2.38% estimated exploitation activity in the next 30 days; percentile 83.90 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A critical unauthenticated remote code execution (RCE) vulnerability exists in the MCP stdio configuration validation introduced in version 2.0.5. The application allows unrestricted user registration, meaning any attacker can create an account and exploit the command injection flaw. Despite implementing a whitelist for allowed commands (npx, uvx) and blacklists for dangerous arguments and environment variables, the validation can be bypassed using the -p flag with npx node. This allows any attacker to execute arbitrary commands with the application's privileges, leading to complete system compromise. The vulnerability remained unfixed across multiple releases (2.0.6-2.0.9) before being silently patched in version 2.0.10, without a published CVE, potentially leaving customers unaware. Details The application's open registration policy, combined with the vulnerable MCP stdio configuration, creates an unrestricted attack surface. Any attacker can: 1. Register a new account…

Published by the source

7 Mar 2026, 01:59 UTC

Last modified by the source

9 Mar 2026, 13:14 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r55h-3rwj-hcmg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-30861

Advisory: WeKnora has Remote Code Execution (RCE) via Command Injection in MCP Stdio Configuration Validation
IDs: CVE-2026-30861, GHSA-r55h-3rwj-hcmg
Record: https://patchnext.com/advisories/cve-2026-30861 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/Tencent/WeKnora 0.2.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/Tencent/WeKnora: affected >= 0.2.5, < 0.2.10; fixed in 0.2.10

## Suggested inspection (read-only)
- Go github.com/Tencent/WeKnora: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/Tencent/WeKnora.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r55h-3rwj-hcmg (GitHub-reviewed advisory GHSA-r55h-3rwj-hcmg lists affected ranges: Go github.com/Tencent/WeKnora >=0.2.5 <0.2.10)

Commands are suggestions: review each one before running it.