PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.59, AgentTeam.launch and the Agents alias register GET /{path}/list, POST /{path}, and `POST /{path}/{agent_id}' without access-control checks before listing agents or calling agent.chat. A remotely exposed server can therefore let unauthenticated clients enumerate agents, consume model resources, access connected private context, and trigger agent tools or workflow side effects. This vulnerability is fixed in praisonaiagents 1.6.59.
CVE-2026-57118
CRITICALPre-NVD 9.89.8ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Also known asEUVD-2026-97774 (ENISA EUVD) · GHSA-x8cv-xmq7-p8xp (GitHub Security Advisories)Source: ENISA EUVD
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8CRITICALmedium confidence
- EG Risk
- 75EG Risk 75/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity98% × 45%Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.4%
- EPSS %ILE
- 35th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
June 18, 2026
Last Modified
October 16, 2026
Advisory Details (3)
Auto-updated Oct 16, 2026🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available
AgentTeam.launch Exposes Unauthenticated Remote Agent Listing and Invocation Endpoints · Advisory · MervinPraison/PraisonAI · GitHub
https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-x8cv-xmq7-p8xpGitHub release Patch Available
PraisonAI v4.6.59
Patch available: MervinPraison/PraisonAI v4.6.59
https://github.com/MervinPraison/PraisonAI/releases/tag/v4.6.59GitHub commit Patch Available
commit b4270173d412 (MervinPraison/PraisonAI)
Patch available: MervinPraison/PraisonAI v4.6.151 (contains commit b4270173d412)
https://github.com/MervinPraison/PraisonAI/commit/b4270173d4123fb1ee8910588f0896668ee21b59Vendor Advisories for CVE-2026-57118(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 | Fix by version range | Dependents |
|---|---|---|---|
| praisonaiagents | 0.0.1 ... 1.6.9 (586 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 36× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-27 14:23 UTCEG score recompute
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-26 14:28 UTCEG score recompute
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-25 14:11 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-24 14:25 UTCEG score recompute
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-23 14:40 UTCEG score recompute
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-22 14:43 UTCEG score recompute
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-21 14:56 UTCEG score recompute
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-20 15:11 UTCEG score recompute
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-19 15:22 UTCEG score recompute
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-18 03:29 UTCEG score recompute
- 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-17 15:51 UTCEG score recompute
- 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-16 14:21 UTCEG score recompute
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
Show 15 moreShow fewer
- 2026-10-15 14:26 UTCEG score recompute
- 2026-10-15 13:51 UTCEG score recompute
- 2026-10-15 03:07 UTCEG score recompute
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-13 23:18 UTCEG score recompute
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-12 19:25 UTCEG score recompute
- 2026-10-12 15:54 UTCEG score recompute
- 2026-10-11 19:37 UTCEG score recompute
- 2026-10-11 16:53 UTCEG score recompute
- 2026-10-11 14:15 UTCEG score recompute
- 2026-07-30 22:31 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
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:praisonaiagents
Frequently asked(5)
What is CVE-2026-57118?
CVE-2026-57118 is a critical-severity vulnerability; its CVE record was published on June 18, 2026. PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.59, AgentTeam.launch and the Agents alias register GET /{path}/list, POST /{path}, and `POST /{path}/{agent_id}' without access-control checks before listing agents or calling agent.chat. A remotely exposed server can therefore…
When was the CVE record for CVE-2026-57118 published?
The CVE record for CVE-2026-57118 was published on June 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-57118 actively exploited?
CVE-2026-57118 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57118?
CVE-2026-57118 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-57118?
A fix for CVE-2026-57118 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57118 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57118
Is Your Infrastructure Affected by CVE-2026-57118?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.