PatchSiren cyber security CVE debrief
CVE-2026-47391 MervinPraison CVE debrief
CVE-2026-47391 is a critical vulnerability in PraisonAI's multi-agent teams system, specifically in its first-party A2A server example. The vulnerability exposes an unauthenticated A2A JSON-RPC endpoint and registers a `calculate(expression)` tool implemented with Python `eval()`, allowing for arbitrary Python execution in the server process. This issue affects deployments following the official A2A example or similar unauthenticated public A2A deployments with unsafe tools.
- Vendor
- MervinPraison
- Product
- PraisonAI
- CVSS
- CRITICAL 9.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-21
- Original CVE updated
- 2026-10-24
- Advisory published
- 2026-07-21
- Advisory updated
- 2026-10-24
Who should care
Defenders of PraisonAI deployments, particularly those using the official A2A example or similar unauthenticated public A2A deployments with unsafe tools, should assess their exposure and take immediate action to mitigate the vulnerability.
Why it matters
CVE-2026-47391 is a critical vulnerability in PraisonAI's multi-agent teams system that allows for arbitrary Python execution in the server process. Defenders of PraisonAI deployments should assess their exposure and take immediate action to mitigate the vulnerability.
- Arbitrary Python execution in the server process
- Potential for confidentiality and integrity impact due to exposure of task history and task cancellation APIs
- Need for verification of affected versions and remediation status
- Potential for lateral movement and escalation of privileges
Technical summary
The vulnerability is caused by the exposure of an unauthenticated A2A JSON-RPC endpoint and the registration of a `calculate(expression)` tool implemented with Python `eval()`. This allows for arbitrary Python execution in the server process. The issue affects deployments following the official A2A example or similar unauthenticated public A2A deployments with unsafe tools, potentially leading to confidentiality and integrity impacts. Defenders of PraisonAI deployments should assess their exposure and take immediate action to mitigate the vulnerability.
Defensive priority
High
Recommended defensive actions
- Immediately update PraisonAI to version 4.6.40 or later
- Disable the unauthenticated A2A JSON-RPC endpoint
- Restrict access to the A2A server example
- Implement authentication and authorization for A2A deployments
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The vulnerability was confirmed by creation of a marker file from an unauthenticated HTTP request. The issue affects deployments following the official A2A example or similar unauthenticated public A2A deployments with unsafe tools.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-47391 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-47391
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-47391 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-47391
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/MervinPraison/PraisonAI/commit/e0fb8e7dd1ee6759c18ed07f436c21dbd9c20747
-
Source reference
Unverified legacy reference
URL: https://github.com/MervinPraison/PraisonAI/pull/1793
-
Source reference
Unverified legacy reference
URL: https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-vg22-4gmj-prxw
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.