PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.59, SpiderTools.scrape_page validates only the initial URL and lets requests.Session.get follow redirects automatically, so a public-looking URL can redirect to a loopback, private, link-local, or metadata address without revalidation. The redirected response body is returned through scrape_page and its extract_links, crawl, and extract_text callers, allowing disclosure from otherwise blocked services. This issue is fixed in praisonaiagents 1.6.59.
CVE-2026-57115
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(low)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
June 18, 2026
Last Modified
September 15, 2026
Advisory Details (2)
Auto-updated Sep 14, 2026PraisonAI v4.6.59
Patch available: MervinPraison/PraisonAI v4.6.59
https://github.com/MervinPraison/PraisonAI/releases/tag/v4.6.59commit b4270173d412 (MervinPraison/PraisonAI)
Patch available: MervinPraison/PraisonAI v4.6.143 (contains commit b4270173d412)
https://github.com/MervinPraison/PraisonAI/commit/b4270173d4123fb1ee8910588f0896668ee21b59Vendor Advisories for CVE-2026-57115(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| praisonaiagents | 0.0.1 ... 1.6.9 (586 versions) | 1.6.59 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-14 19:24 UTCEG score recompute
- 2026-09-14 18:28 UTCEG score recompute
- 2026-09-14 15:22 UTCEG score recompute
- 2026-07-31 05:16 UTCEG score recompute
- 2026-07-26 18:46 UTCEG score recompute
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-20 21:34 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-57115?
When was CVE-2026-57115 disclosed?
Is CVE-2026-57115 actively exploited?
What is the CVSS score of CVE-2026-57115?
How do I remediate CVE-2026-57115?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57115
Is Your Infrastructure Affected by CVE-2026-57115?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.