Skip to main content
VulnerabilityPublished Updated

CVE-2026-39890: PraisonAI Vulnerable to Remote Code Execution via YAML Deserialization in Agent Definition Loading

Affects praisonaiSource GCVE Database

0
Compare
Authoritative record:CVE-2026-39890· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical : upgrade to 4.5.115 as a priority.

Data as of 16 Nov 2026, 16:50 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.5.115
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade praisonai to 4.5.115.

Affected software

ProductAffectedFixed in
PyPIpraisonaiAffected
  • <4.5.115
Fixed in
  • 4.5.115

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in PraisonAI version 4.5.115 that replaces the unsafe js-yaml load method with one using a safe schema (e.g., JSON_SCHEMA). Users should upgrade to version 4.5.115 or later. Additionally, restrict and validate uploads of agent definition files to trusted users and sanitize inputs to prevent malicious YAML content. Avoid using deprecated safeLoad methods and ensure YAML parsing disallows dangerous tags.

Description

PraisonAI versions prior to 4.5.115 are vulnerable to remote code execution due to unsafe YAML deserialization in the AgentService.loadAgentFromFile method. The vulnerability arises from using the js-yaml library's load function without restricting dangerous tags, allowing malicious YAML files to execute arbitrary JavaScript code on the server. An attacker able to upload a crafted agent definition file can trigger this execution, potentially compromising the server fully. A fix is available in version 4.5.115 that uses a safe YAML schema to prevent code execution.

References

Community reviews

Loading reviews…