CVE-2026-57130
CVE-2026-57130 — PraisonAI: IMAP Command Injection via Unsanitized Email Search Parameters
PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.59, src/praisonai-agents/praisonaiagents/tools/email_tools.py interpolates LLM-controlled from_addr, subject, and query values directly into quoted IMAP SEARCH criteria. Embedded quote, backslash, newline, or null characters can escape the intended criterion and alter IMAP operations when search_emails, reply_email, or archive_email is exposed to an agent with configured email credentials, allowing mailbox data access, modification, deletion, or connection disruption. This issue is fixed in praisonaiagents 1.6.59.
Published Updated Sources: 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
Unreported
no source claims exploitation
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
8.1
high
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
PoC
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component
Remediation
The vendor's own words where we have them.
Upgrade praisonaiagents to 1.6.59 or later (pip advisory GHSA-c969-5x3p-vq3v).
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.48 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
None
Confidentiality
High
Integrity
High
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 |
|---|---|---|---|---|---|
| 8.1 | CVSS 3.1 | high | 2.8 | 5.2 | GitHub (CNA), MervinPraison (CNA), GHSA |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')
- Execute Unauthorized Code or Commands
Mitigation: If at all possible, use library calls rather than external processes to recreate the desired functionality.
CWE-20 · Improper Input Validation
- DoS: Crash, Exit, or Restart
- DoS: Resource Consumption (CPU)
- DoS: Resource Consumption (Memory)
- Read Memory
Mitigation: Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses. [REF-1109] [REF-1110] [REF-1111]
Weakness & attack patterns
- CWE-20Improper Input Validation
- CWE-77Command Injection
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1562.003Impair Defenses: Impair Command History Logging
- T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
- T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /praisonai-agents/praisonaiagents/tools/email_tools.py.
- Prioritize edge telemetry for network-reachable praisonaiagents.
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 8.1 (AV:N)
Sep 14, 2026 · NVD
Initial · CVE published
Sep 14, 2026 · NVD
CVE published by MITRE.
Sep 14, 2026 · SOCRadar CTI
Added · GHSA-c969-5x3p-vq3v published (high)
Jun 18, 2026 · GitHub Security Advisory
References
4 on the record
- github.com/MervinPraison/PraisonAI/commit/b4270173d4123fb1ee8910588f0896668ee21b59
Exploit, Third Party Advisory, Mitre
- github.com/MervinPraison/PraisonAI/releases/tag/v4.6.59
Exploit, Third Party Advisory, Mitre
- github.com/MervinPraison/PraisonAI/security/advisories/GHSA-c969-5x3p-vq3v
Exploit, Third Party Advisory
- github.com/advisories/GHSA-c969-5x3p-vq3v
Exploit, Third Party Advisory
Elsewhere on this site
- MervinPraisonevery CVE for this vendor
- pipevery CVE for this vendor
- Remote Code Execsame class
- CWE-20other 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-57130 is PraisonAI: IMAP Command Injection via Unsanitized Email Search Parameters, a high 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-57130. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-57130. 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 8.1 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.