CVE-2026-22688

9.9 CRITICAL

📋 TL;DR

CVE-2026-22688 is a command injection vulnerability in WeKnora that allows authenticated users to inject malicious commands into MCP stdio settings, causing the server to execute arbitrary subprocesses. This affects all WeKnora deployments prior to version 0.2.5. Attackers with authenticated access can achieve remote code execution on the server.

💻 Affected Systems

Products:
  • Tencent WeKnora
Versions: All versions prior to 0.2.5
Operating Systems: All platforms running WeKnora
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated access to WeKnora interface/API

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full server compromise leading to data theft, lateral movement, and persistent backdoor installation

🟠

Likely Case

Authenticated attackers executing arbitrary commands with server privileges, potentially leading to data exfiltration

🟢

If Mitigated

Limited impact if proper network segmentation and least privilege access controls are implemented

🌐 Internet-Facing: HIGH - If WeKnora is exposed to the internet, authenticated users can exploit this vulnerability
🏢 Internal Only: HIGH - Even internally, authenticated users can exploit this vulnerability for privilege escalation

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW - Simple command injection once authenticated

Exploitation requires authenticated access to WeKnora's MCP stdio configuration

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 0.2.5

Vendor Advisory: https://github.com/Tencent/WeKnora/security/advisories/GHSA-78h3-63c4-5fqc

Restart Required: Yes

Instructions:

1. Backup current configuration and data. 2. Stop WeKnora service. 3. Update to version 0.2.5 using package manager or manual installation. 4. Restart WeKnora service. 5. Verify functionality.

🔧 Temporary Workarounds

Restrict MCP stdio configuration access

all

Limit access to MCP stdio configuration settings to trusted administrators only

Network segmentation

all

Isolate WeKnora servers from sensitive systems and limit outbound connections

🧯 If You Can't Patch

  • Implement strict access controls to limit authenticated users who can modify MCP settings
  • Deploy application-level firewall rules to monitor and block suspicious command execution patterns

🔍 How to Verify

Check if Vulnerable:

Check WeKnora version using the application's admin interface or by examining package version

Check Version:

Check WeKnora configuration files or use package manager: dpkg -l | grep weknora or rpm -qa | grep weknora

Verify Fix Applied:

Confirm version is 0.2.5 or later and test that command injection attempts are properly sanitized

📡 Detection & Monitoring

Log Indicators:

  • Unusual subprocess executions from WeKnora
  • Suspicious command strings in MCP configuration logs
  • Multiple failed authentication attempts followed by configuration changes

Network Indicators:

  • Unexpected outbound connections from WeKnora server
  • Command and control traffic patterns

SIEM Query:

source="weknora" AND (event="subprocess_execution" OR event="config_change") AND command="*;*" OR command="*|*" OR command="*`*"

🔗 References

📤 Share & Export