WeKnora Vulnerable to Tool Execution Hijacking via Ambigous Naming Convention In MCP client and Indirect Prompt Injection

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0029, the 21st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 31 Oct 2026, 15:09 UTC First seen by agentprime
2. 31 Oct 2026, 15:09 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-67q9-58vj-32qx
• OSV: GHSA-67q9-58vj-32qx
• github.com/Tencent/WeKnora/security/advisories/GHSA-67q9-58vj-32qx
• nvd.nist.gov/vuln/detail/CVE-2026-30856
• forum.cursor.com/t/mcp-tools-name-collision-causing-cross-service-tool-call-failures/70946
• github.com/Tencent/WeKnora
• modelcontextprotocol-security.io/ttps/tool-poisoning/tool-name-conflict
• www.elastic.co/security-labs/mcp-tools-attack-defense-recommendations#tool-name-collision

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.