CVE-2026-55541

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% 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
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 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 praisonai 4.6.58, praisonai serve agents and praisonai serve unified parse --api-key but _create_agents_app() and _create_unified_app() do not install a credential check. Unauthenticated callers can reach POST /agents and POST /api/v1/agents/{id}/invoke. This issue is fixed in version 4.6.58.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
55(Track)
EG Risk 55/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 computed
Severity88% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

August 25, 2026

Last Modified

August 25, 2026

Advisory Details (3)

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

`--api-key` flag on `praisonai serve` is not properly enforced · Advisory · MervinPraison/PraisonAI · GitHub

Affected: 4.6.34. This bug is in the newer

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-pvxx-r596-f5qj
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.137 (contains commit 2f9677abb2ea)

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

Vendor Advisories for CVE-2026-55541(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 (748 versions)4.6.58

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 12× 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-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 01:59 UTCEG score recompute
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 16:40 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 18:29 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 20:24 UTCEG score recompute
  9. 2026-08-25 19:36 UTCEG score recompute
  10. 2026-08-25 15:21 UTCEG score recompute
  11. 2026-08-25 15:15 UTCEG score recompute
  12. 2026-08-25 15:14 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55541?
CVE-2026-55541 is a high vulnerability published on August 25, 2026. PraisonAI is a multi-agent teams system. Prior to praisonai 4.6.58, praisonai serve agents and praisonai serve unified parse --api-key but createagentsapp() and createunifiedapp() do not install a credential check. Unauthenticated callers can reach POST /agents and POST /api/v1/agents/{id}/invoke.…
When was CVE-2026-55541 disclosed?
CVE-2026-55541 was first published in the National Vulnerability Database on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55541 actively exploited?
CVE-2026-55541 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.4% of all scored CVEs.
What is the CVSS score of CVE-2026-55541?
CVE-2026-55541 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-55541?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55541, 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-55541

Explore →

Is Your Infrastructure Affected by CVE-2026-55541?

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