CVE-2026-22687: Tencent WeKnora · SQL Injection
Affects Tencent WeKnoraSource CVE Database V5
Not known to be exploited · CVSS 5.6 Medium : upgrade to 0.2.5 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% 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:H/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 10 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.
What to do
Upgrade WeKnora and tencent/WeKnora to 0.2.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TencentWeKnora | Affected
| Fixed in
|
GitHubtencent/WeKnorapkg:github/tencent/WeKnoraOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade WeKnora to version 0.2.5 or later, where the vulnerability is patched. 2. Disable the Agent service if it is not required, reducing the attack surface. 3. Implement strict input validation and sanitization on all user-supplied inputs, especially those used in database queries. 4. Employ parameterized queries or prepared statements in the backend to prevent SQL Injection. 5. Restrict database permissions to the minimum necessary for the application to operate, limiting potential damage. 6. Monitor logs for unusual query patterns or repeated failed attempts that may indicate exploitation attempts. 7. Conduct regular security assessments and code reviews focusing on input handling and database interactions. 8. If feasible, deploy Web Application Firewalls (WAFs) with SQL Injection detection rules tailored to WeKnora's query patterns.
Description
WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.2.5, after WeKnora enables the Agent service, it allows users to call the database query tool. Due to insufficient backend validation, an attacker can use prompt‑based bypass techniques to evade query restrictions and obtain sensitive information from the target server and database. This issue has been patched in version 0.2.5.