CVE-2026-57125: PraisonAI: Unauthenticated RCE via Jobs API + Approval Bypass

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
• EPSS 0.6%, percentile 48: FIRST’s model estimates a 0.6% chance of exploitation activity in the next 30 days, higher than 48% of all scored CVEs (low). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes praisonai (PyPI) <= 4.6.48, fixed in 4.6.59; praisonaiagents (PyPI) < 1.6.59, fixed in 1.6.59. Check your lockfile, including transitive dependencies.

What it is

PraisonAI is a multi-agent teams system. Prior to praisonai 4.6.59 and praisonaiagents 1.6.59, the unauthenticated POST /api/v1/runs Jobs API accepts attacker-controlled agentyaml, and the approve field can mark executecommand as YAML-approved before @requireapproval checks critical tools. This chain allows a remote caller to cause a configured language model agent to invoke arbitrary operating-system commands without credentials or operator interaction. This vulnerability is fixed in praisonai 4.6.59 and praisonaiagents 1.6.59 as fixed versions.

From the GitHub advisory

Unauthenticated Remote Code Execution via Jobs API and Approval Bypass in PraisonAI

Summary

An unauthenticated attacker can execute arbitrary OS commands on any server running the PraisonAI Jobs API by submitting a crafted workflow YAML. The attack chains two weaknesses: the /api/v1/runs endpoint requires no credentials, and a top-level approve field in the submitted YAML unconditionally bypasses the @requireapproval safety decorator on dangerous tools such as executecommand.

Ecosystem: pip | Package: praisonai | Affected:

---

Weakness type: CWE-306, CWE-863.

Product: praisonai (PyPI) · Assigned by: GitHub_M · Published: 2026-09-14

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation poc, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 0.60% probability of exploitation activity in the next 30 days; percentile 48.

Timeline

• 2026-06-18 — GitHub-reviewed advisory GHSA-4869-x4pr-q22x published (critical)
• 2026-09-14 — CVE record last updated
• 2026-09-14 — CVE record published by GitHub_M

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-4869-x4pr-q22x github.com
2. CVE.org record CVE-2026-57125 cve.org
3. NVD entry CVE-2026-57125 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com
2. github.com github.com
3. github.com github.com

Critical PyPI advisories · Today’s Security Digest