Security Digest · Vulnerability record

CVE-2026-30855: WeKnora Vulnerable to Broken Access Control in Tenant Management

WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval.

CVSS 8.8 High EPSS 0.5% · p40

Should you act?

Normal patch cycle

No exploitation signal; fix it in your next routine update if you are affected. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
  • EPSS 0.5%, percentile 40: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 40% of all scored CVEs (low). EPSS is a probability, not a verdict.
  • Needs an account (low (any account)). Exposure depends on who can log in.
  • Only applies if your dependency tree includes github.com/Tencent/WeKnora (Go) <= 0.3.1, fixed in 0.3.2. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

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

Details The tenant management handlers do not validate that the caller owns the tenant or has cross-tenant privileges. The handlers parse the tenant ID from the path and directly call the service layer with that ID, returning or mutating the tenant without authorization checks.

Affected handlers: - GET /api/v1/tenants lists all tenants without ownership checks - GET /api/v1/tenants/{id} reads any tenant by ID without ownership checks - PUT /api/v1/tenants/{id} allows updating any tenant by ID without ownership checks - DELETE /api/v1/tenants/{id} allows deleting any tenant by ID without ownership checks

These endpoints do not enforce cross-tenant permissions or deny-by-default behavior, unlike ListAllTenants and SearchTenants.

PoC 1) Register a new account as a user in Tenant 10025 and obtain a bearer token or API key.

Weakness type: CWE-284.

Product: github.com/Tencent/WeKnora (Go) · Assigned by: GitHub_M · Published: 2026-03-07

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
Gogithub.com/Tencent/WeKnora<= 0.3.10.3.2
VendorProductAffected versions (per CVE record)
TencentWeKnora< 0.3.2

Severity scores

Scored byCVSSScoreVector
GitHub_M3.18.8 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub3.19.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: low (any account)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 0.48% probability of exploitation activity in the next 30 days; percentile 40.

Timeline

  • — GitHub-reviewed advisory GHSA-ccj6-79j6-cq5q published (critical)
  • — CVE record published by GitHub_M
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-ccj6-79j6-cq5q github.com
  2. CVE.org record CVE-2026-30855 cve.org
  3. NVD entry CVE-2026-30855 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com

Critical Go advisories · Today’s Security Digest