Skip to main content
VulnerabilityPublished Updated

CVE-2026-22688: Tencent WeKnora · Command Injection

Affects Tencent WeKnoraSource CVE Database V5

0

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

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.9% chance of exploitation in 30 days – higher than 79% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.2.5
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 10 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade WeKnora and tencent/WeKnora to 0.2.5.

Affected software

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

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.5 or later where the vulnerability is patched.
  2. Restrict access to WeKnora management interfaces and APIs to trusted, authenticated users only, employing strong authentication mechanisms such as multi-factor authentication (MFA).
  3. Implement strict input validation and sanitization on any user-supplied parameters related to command or argument configurations, even beyond the vendor patch.
  4. Monitor server logs and subprocess execution patterns for unusual or unauthorized commands indicative of exploitation attempts.
  5. Employ network segmentation to isolate WeKnora servers from critical infrastructure to limit lateral movement in case of compromise.
  6. Conduct regular security audits and penetration testing focused on command injection and privilege escalation vectors.
  7. Educate administrators and users about the risks of credential compromise and enforce strong password policies.
  8. Maintain an incident response plan tailored to rapid containment and remediation of command injection incidents.

Description

WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.2.5, there is a command injection vulnerability that allows authenticated users to inject stdio_config.command/args into MCP stdio settings, causing the server to execute subprocesses using these injected values. This issue has been patched in version 0.2.5.

References

Community reviews

Loading reviews…