CVE-2026-55532

PraisonAI: Origin-validation bypass (startswith prefix match) enables unauthenticated cross-site request forgery against the PraisonAI MCP HTTP server

A developer running the PraisonAI MCP server locally with the default HTTP-stream transport and no API key can be attacked by any web page they visit. The page forges an unauthenticated cross-site request to 127.0.0.1, which passes the Origin allowlist because of the startswith prefix match. The attacker can invoke state-changing MCP tools blind. The most serious demonstrated consequence is persistent prompt injection: the forged request writes a rule that the agent runtime loads with activation "always", so the attacker plants instructions (for example, exfiltrate SSH keys and API keys) that are silently applied to every later agent run, escalating to confidentiality loss on the next invocation. The attacker can also delete the victim's rules, manipulate todos, and schedule attacker-controlled agent tasks. This is a drive-by, unauthenticated, no-direct-network-access compromise of a local agent tool.

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

CVE-2026-55532 has a CVSS score of 7.6 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.6.58); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Replace the prefix match with an exact, parsed-origin comparison: compare the scheme, host, and port of the request Origin against the allowlist (urllib.parse), never startswith. Treat a missing Origin conservatively for state-changing methods rather than allowing it unconditionally, and validate the Host header to defend against DNS rebinding. Strongly consider requiring authentication by default for the HTTP-stream transport (generate and print a token when none is supplied), and reject request bodies whose Content-Type is not application/json so that browser "simple requests" cannot reach the JSON-RPC dispatcher without a preflight. Finally, apply standard CSRF defenses (require a non-simple Content-Type plus a custom header that a cross-site simple request cannot set) on all state-changing tools/call requests.

1. What is CVE-2026-55532? CVE-2026-55532 is a high-severity cross-site request forgery (CSRF) vulnerability in PraisonAI (pip), affecting versions < 4.6.58. It is fixed in 4.6.58. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is CVE-2026-55532? CVE-2026-55532 has a CVSS score of 7.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of PraisonAI are affected by CVE-2026-55532? PraisonAI (pip) versions < 4.6.58 is affected.
4. Is there a fix for CVE-2026-55532? Yes. CVE-2026-55532 is fixed in 4.6.58. Upgrade to this version or later.
5. Is CVE-2026-55532 exploitable, and should I be worried? Whether CVE-2026-55532 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-55532 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-55532? Upgrade PraisonAI to 4.6.58 or later.