Skip to main content
VulnerabilityPublished Updated

CVE-2026-30861: Tencent WeKnora · OS Command Injection

Affects Tencent WeKnoraSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 10.0 Critical : upgrade to 0.2.10 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.2% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.2.10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade WeKnora and tencent/WeKnora to 0.2.10.

Affected software

ProductAffectedFixed in
TencentWeKnoraAffected
  • >=0.2.5 <0.2.10
Fixed in
  • 0.2.10
GitHubtencent/WeKnorapkg:github/tencent/WeKnoraOther threatsAffected
  • >=0.2.5 <0.2.10
Fixed in
  • 0.2.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately upgrade Tencent WeKnora to version 0.2.10 or later, where the vulnerability is patched.
  2. If upgrading is not immediately possible, restrict network access to the WeKnora application to trusted users only, using firewalls or network segmentation.
  3. Implement additional application-layer controls to monitor and block suspicious command execution patterns, especially those involving 'npx' and the '-p' flag.
  4. Enforce strong user registration controls, such as CAPTCHA, email verification, or administrator approval, to reduce automated account creation by attackers.
  5. Conduct thorough logging and monitoring of command execution and user activities within WeKnora to detect potential exploitation attempts.
  6. Review and harden the underlying operating system and container environments hosting WeKnora, applying the principle of least privilege to limit damage from potential compromise.
  7. Educate development teams on secure coding practices, particularly proper input validation and command sanitization to prevent similar injection flaws.
  8. Consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect and block exploitation attempts in real time.

Description

WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. From version 0.2.5 to before version 0.2.10, an unauthenticated remote code execution (RCE) vulnerability exists in the MCP stdio configuration validation. 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. This issue has been patched in version 0.2.10.

References

Community reviews

Loading reviews…