WeKnora Vulnerable to Remote Code Execution via SQL Injection Bypass in AI Database Query Tool

Exploitation

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

CVSS

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

EPSS

• CVE-2026-30860: 0.73% estimated exploitation activity in the next 30 days; percentile 54.47 (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 critical Remote Code Execution (RCE) vulnerability exists in the application's database query functionality. The validation system fails to recursively inspect child nodes within PostgreSQL array expressions and row expressions, allowing attackers to bypass SQL injection protections. By smuggling dangerous PostgreSQL functions inside these expressions and chaining them with large object operations and library loading capabilities, an unauthenticated attacker can achieve arbitrary code execution on the database server with database user privileges. Impact: Complete system compromise with arbitrary code execution --- Details Root Cause Analysis The application implements a 7-phase SQL validation framework in internal/utils/inject.go designed to prevent SQL injection attacks: | Phase | Validation Type | Status | |-------|-----------------|--------| | Phase 1 | Null byte and length checks | ✅ Working | | Phase 2 | PostgreSQL AST parsing via pgquerygo/v6 | ✅ Working | | Phase 3…

Published by the source

6 Mar 2026, 23:59 UTC

Last modified by the source

9 Mar 2026, 13:15 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8w32-6mrw-q5wv

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

# Patch Next advisory brief: CVE-2026-30860

Advisory: WeKnora Vulnerable to Remote Code Execution via SQL Injection Bypass in AI Database Query Tool
IDs: CVE-2026-30860, GHSA-8w32-6mrw-q5wv
Record: https://patchnext.com/advisories/cve-2026-30860 (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 10.0)
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.2.12. A vendor fix does not mean a deployment is fixed.

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

## 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-8w32-6mrw-q5wv (GitHub-reviewed advisory GHSA-8w32-6mrw-q5wv lists affected ranges: Go github.com/Tencent/WeKnora >=0 <=0.2.11)

Commands are suggestions: review each one before running it.