CVE-2026-57127

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 42% of all CVEs by exploit prediction. 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

PraisonAI is a multi-agent teams system. Prior to 4.6.58, recipe serve installs APIKeyAuthMiddleware or JWTAuthMiddleware when an operator selects api-key or JWT authentication, but each middleware forwards requests when PRAISONAI_API_KEY or PRAISONAI_JWT_SECRET and the corresponding recipe value are absent. Unauthenticated clients can then reach recipe execution, input, and output surfaces and may trigger connected tools despite the operator explicitly enabling authentication. This issue is fixed in 4.6.58.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

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 computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

Published

June 18, 2026

Last Modified

September 16, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

praisonai: recipe serve auth middleware silently disables itself when no secret is set (CWE-306) · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-j4hj-7hfh-g2f4
github_release Patch Available

PraisonAI v4.6.58

Patch available: MervinPraison/PraisonAI v4.6.58

https://github.com/MervinPraison/PraisonAI/releases/tag/v4.6.58
github_commit Patch Available

commit 2f9677abb2ea (MervinPraison/PraisonAI)

Patch available: MervinPraison/PraisonAI v4.6.144 (contains commit 2f9677abb2ea)

https://github.com/MervinPraison/PraisonAI/commit/2f9677abb2ea68eab864ee8b6a828fd0141612e1

Vendor Advisories for CVE-2026-57127(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)
PackageVulnerable rangeFixed inDependents
praisonai0.0.1 ... 4.6.9 (749 versions)4.6.59

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× 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.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 13:47 UTCEG score recompute
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-14 18:09 UTCEG score recompute
  7. 2026-09-14 16:50 UTCEG score recompute
  8. 2026-09-14 16:27 UTCEG score recompute
  9. 2026-07-30 22:31 UTCEG score recompute
  10. 2026-07-26 18:46 UTCEG score recompute
  11. 2026-07-23 03:20 UTCEG score recompute
  12. 2026-07-20 21:34 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-57127?
CVE-2026-57127 is a critical vulnerability published on June 18, 2026. PraisonAI is a multi-agent teams system. Prior to 4.6.58, recipe serve installs APIKeyAuthMiddleware or JWTAuthMiddleware when an operator selects api-key or JWT authentication, but each middleware forwards requests when PRAISONAIAPIKEY or PRAISONAIJWTSECRET and the corresponding recipe value are…
When was CVE-2026-57127 disclosed?
CVE-2026-57127 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57127 actively exploited?
CVE-2026-57127 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 41.9% of all scored CVEs.
What is the CVSS score of CVE-2026-57127?
CVE-2026-57127 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-57127?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57127, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57127

Explore →

Is Your Infrastructure Affected by CVE-2026-57127?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.