CVE-2026-57126
CVE-2026-57126 — praisonaiagents: SSRF guard validates literal IPs only and never resolves DNS
PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.58, SpiderTools._validate_url calls _host_is_blocked, which checks literal host encodings but does not resolve DNS names before scrape_page, crawl, extract_links, extract_text, or URL-mention fetches connect. An attacker-controlled hostname resolving to a loopback, private, link-local, or cloud-metadata address therefore bypasses the SSRF policy without a rebinding race and can expose internal responses to the agent. This issue is fixed in praisonaiagents 1.6.58.
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
Exploit code
public exploit, none observed
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
8.5
high
Remediation
The vendor's own words where we have them.
Upgrade praisonaiagents to 1.6.59 or later (pip advisory GHSA-vxgj-xg5c-p4h7).
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 | PraisonAI | < 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
Low
Scope
Changed
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.5 | CVSS 3.1 | high | 3.1 | 4.7 | GitHub (CNA), MervinPraison (CNA), GHSA |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/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-918 · Server-Side Request Forgery (SSRF)
- Read Application Data
- Execute Unauthorized Code or Commands::
Weakness & attack patterns
- CWE-918Server-Side Request Forgery (SSRF)
Inferred from the weakness class — not observed against this CVE.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
3
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Prioritize edge telemetry for network-reachable PraisonAI, praisonaiagents.
- Monitor for scanner or exploit-pattern traffic after 3 public PoC repositories were reported.
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.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-vxgj-xg5c-p4h7 published (high)
Jun 18, 2026 · GitHub Security Advisory
References
4 on the record
- github.com/MervinPraison/PraisonAI/commit/2f9677abb2ea68eab864ee8b6a828fd0141612e1
Exploit, Third Party Advisory, Mitre
- github.com/MervinPraison/PraisonAI/releases/tag/v4.6.58
Exploit, Third Party Advisory, Mitre
- github.com/MervinPraison/PraisonAI/security/advisories/GHSA-vxgj-xg5c-p4h7
Exploit, Third Party Advisory, Mitre
- github.com/advisories/GHSA-vxgj-xg5c-p4h7
Exploit, Third Party Advisory
Elsewhere on this site
- MervinPraisonevery CVE for this vendor
- pipevery CVE for this vendor
- SSRFsame class
- CWE-918other 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-57126 is praisonaiagents: SSRF guard validates literal IPs only and never resolves DNS, a high vulnerability affecting PraisonAI, 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-57126. Public exploit evidence is: 3 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 8.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.