CVE-2026-30859: GO-2026-4637 - WeKnora has Broken Access Control - Cross-Tenant Data Exposure in github.com/Tencent/WeKnora

CVE-2026-30859 · Severity: low · CVSS 3.1 · Published 2026-03-10

WeKnora has Broken Access Control - Cross-Tenant Data Exposure in github.com/Tencent/WeKnora

Technologies: github.com/Tencent/WeKnora (Go). Vendors: Go.

Quick answers

Is CVE-2026-30859 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-30859 being exploited in the wild.
How severe is CVE-2026-30859?
Low severity, with a CVSS score of 3.1, published 10 March 2026.
Which products and versions are affected?
github.com/Tencent/WeKnora (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=0.2.12.
Is there a fix for CVE-2026-30859?
Yes. github.com/Tencent/WeKnora (Go): upgrade to 0.2.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-30859?
Check whether you run github.com/Tencent/WeKnora (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/Tencent/WeKnora (Go): upgrade to 0.2.12 or later
    go get github.com/Tencent/WeKnora@v0.2.12

Affected products

  • github.com/Tencent/WeKnora (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=0.2.12

Identifiers

  • CVE-2026-30859
  • GHSA-2f4c-vrjq-rcgv
  • GO-2026-4637

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.