Advisory record · GHSA-ccj6-79j6-cq5q

WeKnora Vulnerable to Broken Access Control in Tenant Management

CVSS 8.8 HighEPSS 0.0038 · 32nd percentile

Published by the GitHub Advisory Database at 6 Mar 2026, 23:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/Tencent/WeKnoraGo<0.3.20.3.2
Identifiers
GHSA-ccj6-79j6-cq5q · CVE-2026-30855 · GO-2026-4642
Weakness (CWE)
CWE-284
Published
6 Mar 2026
Updated
23 Mar 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

WeKnora (Go package github.com/Tencent/WeKnora) versions before 0.3.2 have a broken access control flaw in its tenant management endpoints, which do not check whether the caller owns the tenant being read, changed, or deleted. Any user who can register an account, which the source says is open to the public, can read, modify, or delete other tenants by ID, including their LLM API keys and knowledge bases. Upgrade to version 0.3.2 or later.

Written 7 Nov 2026.

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

ScoreRatingCVSSVectorSource
8.8 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0038, the 32nd percentile, on 19 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

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.