Security Digest · Vulnerability record
CVE-2026-22688: WeKnora has Command Injection in MCP stdio test
WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval.
CVSS 10.0 Critical EPSS 1.9% · p80
Should you act?
Critical, preconditions apply
Severe if exploited, but exploitation needs conditions that may not apply to you. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 1.9%, percentile 80: FIRST’s model estimates a 1.9% chance of exploitation activity in the next 30 days, higher than 80% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Needs an account (low (any account)). Exposure depends on who can log in.
- Only applies if your dependency tree includes
github.com/Tencent/WeKnora(Go) < 0.2.5, fixed in 0.2.5. Check your lockfile, including transitive dependencies.
What it is
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 stdioconfig.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.
From the GitHub advisory
Vulnerability Description
---
Vulnerability Overview
This issue is a command injection vulnerability (CWE-78) that allows authenticated users to inject stdioconfig.command/args into MCP stdio settings, causing the server to execute subprocesses using these injected values.
The root causes are as follows:
Weakness type: CWE-77.
Product: github.com/Tencent/WeKnora (Go) · Assigned by: GitHub_M · Published: 2026-01-10
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| Go | github.com/Tencent/WeKnora | < 0.2.5 | 0.2.5 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| Tencent | WeKnora | < 0.2.5 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_M | 3.1 | 10 Critical | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: low (any account)
- User interaction: none
- Scope: changed (can affect other components)
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
- FIRST EPSS (model of 2026-10-21): 1.94% probability of exploitation activity in the next 30 days; percentile 80.
Timeline
- — GitHub-reviewed advisory GHSA-78h3-63c4-5fqc published (critical)
- — CVE record published by GitHub_M
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-78h3-63c4-5fqc github.com
- CVE.org record CVE-2026-22688 cve.org
- NVD entry CVE-2026-22688 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com
- github.com github.com
- pkg.go.dev pkg.go.dev