CVE-2026-30860: Tencent WeKnora · SQL Injection
Affects Tencent WeKnoraSource CVE Database V5
Not known to be exploited · CVSS 10.0 Critical : upgrade to 0.2.12 as a priority.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.2.12
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Upgrade WeKnora and tencent/WeKnora to 0.2.12.
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
To mitigate CVE-2026-30860, organizations should immediately upgrade Tencent WeKnora to version 0.2.12 or later, where the vulnerability is patched. Additionally, organizations should: 1) Review and restrict database user privileges to the minimum necessary to limit potential damage from exploitation. 2) Implement network segmentation and firewall rules to restrict external access to the database server and WeKnora application interfaces. 3) Monitor database logs and application logs for unusual queries or large object operations that may indicate exploitation attempts. 4) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious PostgreSQL function calls or malformed array/row expressions. 5) Conduct regular security audits and code reviews focusing on input validation and SQL query construction. 6) Consider deploying runtime application self-protection (RASP) solutions to detect and prevent SQL injection attacks in real time. 7) Educate developers and administrators about secure coding practices related to SQL query handling, especially with complex PostgreSQL data types. These targeted measures, combined with patching, will reduce the risk of exploitation and limit potential damage.
Description
WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.2.12, a remote code execution (RCE) vulnerability exists in the application's database query functionality. The validation system fails to recursively inspect child nodes within PostgreSQL array expressions and row expressions, allowing attackers to bypass SQL injection protections. By smuggling dangerous PostgreSQL functions inside these expressions and chaining them with large object operations and library loading capabilities, an unauthenticated attacker can achieve arbitrary code execution on the database server with database user privileges. This issue has been patched in version 0.2.12.