# WeKnora Vulnerable to Broken Access Control in Tenant Management

Advisory record · `GHSA-ccj6-79j6-cq5q`

- **Identifiers:** `GHSA-ccj6-79j6-cq5q` · `CVE-2026-30855` · `GO-2026-4642`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 6 Mar 2026
- **Updated:** 23 Mar 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `github.com/Tencent/WeKnora` (Go): affected `<0.3.2`; fixed in `0.3.2`

## 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

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from 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

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-ccj6-79j6-cq5q)

## Sources

- [GitHub Advisory Database: GHSA-ccj6-79j6-cq5q](https://github.com/advisories/GHSA-ccj6-79j6-cq5q)
- [OSV: GHSA-ccj6-79j6-cq5q](https://osv.dev/vulnerability/GHSA-ccj6-79j6-cq5q)
- <https://github.com/Tencent/WeKnora/security/advisories/GHSA-ccj6-79j6-cq5q>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-30855>
- <https://github.com/Tencent/WeKnora>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-ccj6-79j6-cq5q>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-ccj6-79j6-cq5q/>. Everything for agents: <https://agentprime.io/llms.txt>.
