CVE-2026-47391
Unauthenticated A2A endpoint allows remote arbitrary Python execution via eval-based tool.
Is CVE-2026-47391 being exploited?
Not confirmed. CVE-2026-47391 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.2% probability of exploitation in the next 30 days.
How severe is CVE-2026-47391?
CVE-2026-47391 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-47391?
Yes. A fix has been recorded for CVE-2026-47391. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-47391 affect?
CVE-2026-47391 affects PraisonAI A2A example deployments (<4.6.40), Servers binding A2A to 0.0.0.0, LLM-integrated instances (e.g., gemini-2.5 example). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47391?
Upgrade to PraisonAI 4.6.40, restrict A2A to authenticated/local interfaces, remove eval-based tools
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated attacker can invoke an LLM-registered calculate(tool) that uses Python eval(), achieving arbitrary code execution, data exposure, and task tampering.
Immediate action required
- affected< 4.6.40
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.