What is CVE-2026-57120?

CVE-2026-57120 is PraisonAI: execute_code sandbox bypass: str.format C-level attribute access reads every blocklisted dunder. The supplied enrichment data classifies it as Unclassified mapped to CWE-693 CWE-693.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-57120. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-57120 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

1 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-57120 using CVSS 6.5, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

mediumpublic exploit

CVE-2026-57120

CVE-2026-57120 — PraisonAI: execute_code sandbox bypass: str.format C-level attribute access reads every blocklisted dunder

PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.59, execute_code sandbox mode permits runtime assembly of blocklisted dunder names and allows str.format or str.format_map to resolve dotted fields through C-level attribute access that bypasses _safe_getattr. This exposes class, qualified-name, base-class, globals, and object-dictionary attributes to prompt-influenced code when approval is automatically granted, producing a high-impact read primitive without establishing a complete in-process execution chain. This issue is fixed in praisonaiagents 1.6.59.

Published Sep 14, 2026Updated Sep 14, 2026Sources: NVD, MervinPraison (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

MervinPraison

2 products listed

CVSS base

6.5

medium

Remediation

The vendor's own words where we have them.

Upgrade praisonaiagents to 1.6.59 or later (pip advisory GHSA-pv2j-rghr-v5r9).

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
MervinPraison	praisonaiagents	< 1.6.59	Vulnerable
pip	praisonaiagents	< 1.6.59	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

High

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
6.5	CVSS 3.1	medium	2.8	3.6	GitHub (CNA), MervinPraison (CNA), GHSA

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-693 · Protection Mechanism Failure

Bypass Protection Mechanism::

Weakness & attack patterns

CWE-693

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-1 · Accessing Functionality Not Properly Constrained by ACLsCAPEC-107 · Cross Site TracingCAPEC-127 · Directory IndexingCAPEC-17 · Using Malicious FilesCAPEC-20 · Encryption Brute ForcingCAPEC-22 · Exploiting Trust in ClientCAPEC-237 · Escaping a Sandbox by Calling Signed Code in Another LanguageCAPEC-36 · Using Unpublished InterfacesCAPEC-477 · Signature Spoofing by Mixing Signed and Unsigned ContentCAPEC-480 · Escaping VirtualizationCAPEC-51 · Poison Web Service RegistryCAPEC-57 · Utilizing REST's Trust in the System Resource to Obtain Sensitive Data

T1574.010Hijack Execution Flow: ServicesFile Permissions Weakness
T1083File and Directory Discovery
T1574.005Hijack Execution Flow: Executable Installer File Permissions Weakness

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable praisonaiagents.
Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 6.5 (AV:N)
Sep 14, 2026 · NVD
Initial · CVE published
Sep 14, 2026 · NVD
CVE published by MITRE.
Sep 14, 2026 · SOCRadar CTI
Added · GHSA-pv2j-rghr-v5r9 published (medium)
Jun 18, 2026 · GitHub Security Advisory

References

4 on the record

github.com/MervinPraison/PraisonAI/commit/2adfe7e8323f6deec66925cf15a885b6238895e9
Exploit, Third Party Advisory, Mitre
github.com/MervinPraison/PraisonAI/releases/tag/v4.6.59
Exploit, Third Party Advisory
github.com/MervinPraison/PraisonAI/security/advisories/GHSA-pv2j-rghr-v5r9
Exploit, Third Party Advisory
github.com/advisories/GHSA-pv2j-rghr-v5r9
Exploit, Third Party Advisory

Elsewhere on this site

MervinPraisonevery CVE for this vendor
pipevery CVE for this vendor
Unclassifiedsame class
CWE-693other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-57120 is PraisonAI: execute_code sandbox bypass: str.format C-level attribute access reads every blocklisted dunder, a medium vulnerability affecting praisonaiagents from MervinPraison, pip. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-57120. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.5 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.