dbcve.org
WeknoraApplication · Tencent

CVE-2026-22687

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-10
Fix available
A fix is available. Upgrade to 0.2.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.2.5, after WeKnora enables the Agent service, it allows users to call the database query tool. Due to insufficient backend validation, an attacker can use prompt‑based bypass techniques to evade query restrictions and obtain sensitive information from the target server and database. This issue has been patched in version 0.2.5.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

WeKnora versions before 0.2.5 contain a critical prompt injection vulnerability in the Agent service's database query tool. Attackers can bypass insufficient backend validation using malicious prompts to execute unauthorized database queries and exfiltrate sensitive server and database information.

MitigationUpgrade WeKnora to version 0.2.5 or later to apply the patch that addresses the insufficient backend validation in the Agent service database query functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WeknoraApplication
Affected:< 0.2.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Weknora version
    Locate the Weknora installation directory and check the version metadata file or use the version command if available in the CLI. Common locations include the application root directory or package manager records.
    Affected if The installed version is lower than 0.2.5 (e.g., 0.2.4, 0.2.3, etc.)
  2. Confirm Agent service is enabled
    Inspect the Weknora configuration files or service settings to verify that the Agent service component is active and accessible. Look for Agent-related configuration entries in the main config file or service registry.
    Affected if The Agent service is enabled and running, and the version is below 0.2.5
  3. Verify database query tool functionality is accessible
    Check if the Agent service's database query tool endpoint or interface is exposed and operational. This may be visible in the API documentation, service configuration, or through the administration panel.
    Affected if The database query tool functionality is available in the Agent service and the version is below 0.2.5
  4. Review backend validation configuration
    Examine the Agent service configuration files for any validation-related settings controlling prompt processing for database queries. Look for entries related to input sanitization or query restriction.
    Affected if Backend validation settings are present but the version is below 0.2.5, indicating the vulnerable configuration may exist

You are affected if Weknora version is below 0.2.5 AND the Agent service with its database query tool is enabled and accessible in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.2.5 or later
Fixed in 0.2.5
Vendor patch github.com →
Interim mitigation

Upgrade WeKnora to version 0.2.5 or later to apply the patch that addresses the insufficient backend validation in the Agent service database query functionality.

Recommended fix High confidence

0.2.5

  1. Upgrade WeKnora to version 0.2.5 or later by pulling the latest release from the GitHub repository
  2. Verify the installation by checking the version number matches or exceeds 0.2.5
  3. After upgrading, test that the Agent service database query tool properly validates and restricts user input
  4. Confirm that prompt-based bypass techniques no longer allow unauthorized database access

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Weknora Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22687 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22687 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data