WeKnora Vulnerable to Broken Access Control in Tenant Management

Exploitation

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

CVSS

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

EPSS

• CVE-2026-30855: 0.38% estimated exploitation activity in the next 30 days; percentile 31.72 (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 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…

Published by the source

6 Mar 2026, 23:53 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-ccj6-79j6-cq5q

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

# Patch Next advisory brief: CVE-2026-30855

Advisory: WeKnora Vulnerable to Broken Access Control in Tenant Management
IDs: CVE-2026-30855, GHSA-ccj6-79j6-cq5q
Record: https://patchnext.com/advisories/cve-2026-30855 (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: Critical (CVSS 9.8)
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.2. A vendor fix does not mean a deployment is fixed.

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

## 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-ccj6-79j6-cq5q (GitHub-reviewed advisory GHSA-ccj6-79j6-cq5q lists affected ranges: Go github.com/Tencent/WeKnora >=0 <=0.3.1)

Commands are suggestions: review each one before running it.