Skip to main content
VulnerabilityPublished Updated

CVE-2026-30855: Tencent WeKnora · Improper Access Control

Affects Tencent WeKnoraSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 0.3.2 soon.

Data as of 30 Oct 2026, 11:52 UTC

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

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

Affected software

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

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

AI-suggested

  1. Immediately upgrade WeKnora to version 0.3.2 or later where the authorization bypass is patched.
  2. Until upgrade is possible, restrict or disable public account registration to prevent unauthorized authenticated access.
  3. Implement additional access control layers at the application or infrastructure level to enforce tenant isolation, such as API gateways or web application firewalls with tenant-aware rules.
  4. Conduct thorough audits of tenant management endpoints and logs to detect suspicious cross-tenant access or modifications.
  5. Employ monitoring and alerting on unusual tenant activity patterns indicative of exploitation attempts.
  6. Review and harden authentication and authorization mechanisms, ensuring least privilege principles are enforced.
  7. Educate development and security teams on secure multi-tenant design principles to prevent similar flaws.
  8. Consider network segmentation or zero-trust models to limit lateral movement if compromise occurs.

Description

WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.3.2, an authorization bypass in tenant management endpoints of WeKnora application allows any authenticated user to read, modify, or delete any tenant by ID. Since account registration is open to the public, this vulnerability allows any unauthenticated attacker to register an account and subsequently exploit the system. This enables cross-tenant account takeover and destruction, making the impact critical. This issue has been patched in version 0.3.2.

References

Community reviews

Loading reviews…