$ research-item --score 47 --exploit none

WeKnora is an LLM-powered framework designed for deep document understanding …

Research page generated from configured evidence sources. Treat this as an analyst workbench: facts are sourced, gaps are labelled, and low-confidence chatter is separated from confirmed evidence.

Executive judgement

  • Priority score: 47
  • Confidence: high
  • Exploit status: none — No public exploitation signal captured by the configured pipeline yet.
  • CISA KEV: No CISA KEV match captured in configured source data at generation time.
  • Published/observed: 2026-03-07

What happened

WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. From version 0.2.5 to before version 0.2.10, an unauthenticated remote code execution (RCE) vulnerability exists in the MCP stdio configuration validation. The application allows unrestricted user registration, meaning any attacker can create an account and exploit the command injection flaw. Despite implementing a whitelist for allowed commands (npx, uvx) and blacklists for dangerous arguments and environment variables, the validation can be bypassed using the -p flag with npx node. This allows any attacker to execute arbitrary commands with the application’s privileges, leading to complete system compromise. This issue has been patched in version 0.2.10.

Why it matters

  • The item was promoted because the pipeline observed: priority score 47, exploit status none, confidence high.
  • It has a CVE identifier, so it can be tracked across NVD/CVE.org/vendor/exploit sources.
  • No PoC signal was detected by the current pipeline unless shown elsewhere on this page.

Evidence collected

Exploitation and PoC status

  • Current automated assessment: No public exploitation signal captured by the configured pipeline yet.
  • Public exploit/PoC: No PoC source captured yet by the configured pipeline.
  • Exploited in the wild: Not confirmed by configured sources at generation time.
  • Ransomware association: No ransomware association captured at generation time.

Dark web / low-confidence chatter

Defender actions

  • Upgrade WeKnora to version 0.2.10 or later.
  • If immediate upgrade is not possible, disable user registration in the WeKnora configuration (if supported) or implement an application-layer firewall rule to block the registration endpoint.
  • Audit system logs for execution of ’npx’ or ‘uvx’ commands with the ‘-p’ flag originating from the WeKnora application process.

Exposure validation ideas

  • Search asset inventory for affected vendor/product names and any CVE reference.
  • Check internet-facing exposure through approved tools only: Shodan/Censys/GreyNoise links below are research starting points, not proof of exposure.
  • Prioritise management interfaces, edge devices, identity/control-plane systems, and OT/ICS assets where relevant.

Detection / hunting ideas

  • Review vendor logs for authentication failures, privilege changes, unexpected admin activity, and anomalous management-plane access.
  • Search SIEM/EDR telemetry for product-specific process names, network services, and newly published indicators from primary sources.
  • Monitor for scanner traffic or nuclei/metasploit module references once public exploit tooling appears.

Open questions

  • Is there a primary vendor advisory with exact affected versions and fixed versions?
  • Has CISA KEV, Shadowserver, GreyNoise, or a trusted vendor confirmed exploitation?
  • Are there credible PoC repositories or only secondary reporting mentioning PoC?
  • Is there underground/forum/leak-site discussion, or only public reporting?

Generated: 2026-06-05T09:27:22+00:00

← back to today