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
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.
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.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| praisonai | PyPI | >= 4.6.56, <= 4.6.58 | 4.6.59 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- CriticalPraisonAI: AICoder Arbitrary File Write and Command Execution via LLM Tool Callspraisonai
- CriticalPraisonAI: Code Injection via f-string Interpolation in Deploy API Server Generationpraisonai
- CriticalPraisonAI has a Browser Server WebSocket origin validation bypass via unanchored regex (patch bypass of CVE-2026-40289 / GHSA-8x8f-54wf-vv92praisonai
- CriticalPraisonAI: Arbitrary File Read/Write via `multiedit` Tool Without Path Validationpraisonai
- CriticalPraisonAI: Unauthenticated RCE via Jobs API + Approval Bypasspraisonaiagents, praisonai
- CriticalPraisonAI: AgentOS remains unauthenticated after incomplete fix version and allows remote agent invocationpraisonai
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.