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

> An authorization bypass in WeKnora allows any registered user to read, modify, or delete any tenant, enabling cross-tenant account takeover and data destruction.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-ccj6-79j6-cq5q, GO-2026-4642

## What is CVE-2026-30855?

CVE-2026-30855 is a high-severity missing authorization vulnerability in Tencent WeKnora, published on 7 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-30855?

3 open source packages ship an affected version, including github.com/Tencent/WeKnora. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/Tencent/WeKnora` | Go | All versions | 0.3.1 |
| `github.com/Tencent/WeKnora` | Go | All versions | 0.3.2 |
| `github.com/Tencent/WeKnora` | Go | All versions | 0.3.2 |

Products: Tencent Weknora.

## How do I fix CVE-2026-30855?

Upgrade github.com/Tencent/WeKnora to a fixed version for your release line: 0.3.1 or 0.3.2.

## Is CVE-2026-30855 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30855 exists.

## Other vulnerabilities in Tencent WeKnora

- [CVE-2026-30860](https://insights.sbomify.com/CVE-2026-30860/): WeKnora: Remote Code Execution via SQL Injection Bypass in AI Database Query Tool (critical 10.0)
- [CVE-2026-30861](https://insights.sbomify.com/CVE-2026-30861/): WeKnora: Remote Code Execution (RCE) via Command Injection in MCP Stdio Configuration Validation (critical 10.0)
- [CVE-2026-22688](https://insights.sbomify.com/CVE-2026-22688/): WeKnora has Command Injection in MCP stdio test (critical 10.0)
- [CVE-2025-11046](https://insights.sbomify.com/CVE-2025-11046/): Tencent WeKnora test testEmbeddingModel server-side request forgery (medium 6.9)
- [CVE-2026-30858](https://insights.sbomify.com/CVE-2026-30858/): WeKnora: DNS Rebinding Vulnerability in web_fetch Tool Allows SSRF to Internal Resources (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30855 and fix it if it is affected.

What it is: CVE-2026-30855 is a high-severity missing authorization vulnerability in Tencent WeKnora, published on 7 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30855 exists.

Affected packages and fixed versions:
- github.com/Tencent/WeKnora (Go): affected all versions; fixed in 0.3.1
- github.com/Tencent/WeKnora (Go): affected all versions; fixed in 0.3.2
- github.com/Tencent/WeKnora (Go): affected all versions; fixed in 0.3.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30855/ (Markdown: https://insights.sbomify.com/CVE-2026-30855/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30855
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30855
- OSV: https://osv.dev/vulnerability/CVE-2026-30855

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30855/
Summaries are generated and may contain mistakes; the official description above is the record.