UTC
High

PraisonAI LinearBot processes unsigned webhooks when LINEAR_WEBHOOK_SECRET is missing

CVE-2026-56837 · GHSA-fc26-m9pf-v56q · published 2026-06-18 · updated 2026-07-20

Severity
High
CVSS score
8.6
Chance of exploitation (EPSS)
0.19%
Fixed in
4.6.59
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Partial
  • CISA SSVC
What it is

If a PraisonAI operator starts LinearBot with a Linear token but omits LINEARWEBHOOKSECRET, any network caller that can reach the webhook endpoint can spoof Linear webhook events and invoke the configured agent through the Linear integration. For the AgentSession event path, this lets the attacker supply issue title and description content that becomes the agent input. Depending on the configured agent and tools, this can cause unauthorized LLM/tool execution, consume paid model quota, create or update Linear comments under the bot identity, and drive the bot into workflows intended only for authenticated Linear events. This report does not claim arbitrary code execution by default.

What to do

Upgrade praisonai to 4.6.59 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Fail closed for public webhook listeners: 1. Refuse to start LinearBot when LINEARWEBHOOKSECRET is missing, unless an explicit development-only option such as , reject requests when no signing secret is configured instead of silently skipping verification. 3. Preserve raw-body HMAC verification and constant-time comparison for the configured-secret path. 4. Treat timestamp freshness as replay protection after signature validation, not as a replacement for authentication. 5. Prefer loopback binding by default, or require an explicit host flag for public binding. 6.

Affected
PackageRegistryAffectedFixed in
praisonaiPyPI>= 4.6.56, <= 4.6.584.6.59

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].