WeKnora has Unauthorized Cross‑Tenant Knowledge Base Cloning

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-30857: 0.26% estimated exploitation activity in the next 30 days; percentile 17.17 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A cross-tenant authorization bypass in the knowledge base copy endpoint allows any authenticated user to clone (duplicate) another tenant’s knowledge base into their own tenant by knowing/guessing the source knowledge base ID. This enables bulk data exfiltration (document/FAQ content) across tenants, making the impact critical. Details The POST /api/v1/knowledge-bases/copy endpoint enqueues an asynchronous KB clone task using the caller-supplied sourceid without verifying ownership (see internal/handler/knowledgebase.go). Then, the asynq task handler (ProcessKBClone) invokes the CopyKnowledgeBase service method to perform the clone operation (see internal/application/service/knowledge.go): After that, the CopyKnowledgeBase method calls the repository method to load the source knowledge base (see internal/application/service/knowledgebase.go): Note: until now, the tenant ID is correctly set in context to the attacker’s tenant (from the payload), which can be used to prevent…

Published by the source

6 Mar 2026, 23:55 UTC

Last modified by the source

9 Mar 2026, 13:21 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8rf9-c59g-f82f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-30857

Advisory: WeKnora has Unauthorized Cross‑Tenant Knowledge Base Cloning
IDs: CVE-2026-30857, GHSA-8rf9-c59g-f82f
Record: https://patchnext.com/advisories/cve-2026-30857 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/Tencent/WeKnora 0.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/Tencent/WeKnora: affected <= 0.2.14; fixed in 0.3.0

## Suggested inspection (read-only)
- Go github.com/Tencent/WeKnora: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/Tencent/WeKnora.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8rf9-c59g-f82f (GitHub-reviewed advisory GHSA-8rf9-c59g-f82f lists affected ranges: Go github.com/Tencent/WeKnora >=0 <=0.2.14)

Commands are suggestions: review each one before running it.