Skip to main content
VulnerabilityPublished Updated

CVE-2026-30856: Tencent WeKnora · Use of Incorrectly-Resolved Name or Reference

Affects Tencent WeKnoraSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 0.3.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

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

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.3.0.

Affected software

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

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

AI-suggested

  1. Upgrade all WeKnora deployments to version 0.3.0 or later, where the vulnerability is patched.
  2. Implement strict validation and sanitization of tool names during MCP client registration to prevent name collisions.
  3. Restrict network access to MCP servers to trusted entities only, minimizing exposure to malicious remote servers.
  4. Monitor MCP tool registration logs for suspicious or unexpected tool names that could indicate attempted exploitation.
  5. Employ network segmentation and zero-trust principles around systems running WeKnora to limit lateral movement if compromised.
  6. Educate users and administrators about the risks of interacting with untrusted MCP servers and tools.
  7. Conduct regular security audits and penetration testing focused on LLM frameworks and their integration points to detect similar vulnerabilities early.

Description

WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.3.0, a vulnerability involving tool name collision and indirect prompt injection allows a malicious remote MCP server to hijack tool execution. By exploiting an ambiguous naming convention in the MCP client (mcp_{service}_{tool}), an attacker can register a malicious tool that overwrites a legitimate one (e.g., tavily_extract). This enables the attacker to redirect LLM execution flow, exfiltrate system prompts, context, and potentially execute other tools with the user's privileges. This issue has been patched in version 0.3.0.

References

Community reviews

Loading reviews…