CVE-2026-57128
CVE-2026-57128 — PraisonAI: Unauthenticated Event Injection via SSE `/publish` Endpoint
PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.58, the SSE server in src/praisonai-agents/praisonaiagents/server/server.py does not consult ServerConfig.auth_token before handling /publish, /events, or /info requests. A network client that can reach the server can broadcast arbitrary events to connected clients and obtain server configuration and client-count information. 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
Unreported
no source claims exploitation
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
4.3
medium
Remediation
The vendor's own words where we have them.
Upgrade praisonaiagents to 1.6.59 or later (pip advisory GHSA-35w5-pcw4-jx94).
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.58 | 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
None
Integrity
Low
Scope
Unchanged
Attack Complexity
Low
Attack Vector
Adjacent
Privileges Req
None
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 |
|---|---|---|---|---|---|
| 4.3 | CVSS 3.1 | medium | 2.8 | 1.4 | GitHub (CNA), MervinPraison (CNA), GHSA |
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/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-306 · Missing Authentication for Critical Function
- Gain Privileges or Assume Identity
- Other
Mitigation: Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability. Identify all potential communication channels, or other means of interaction with the software, to ensure that all channels are appropriately protected. Developers sometimes perform authentication at the primary channel, but open up a secondary channel that is assumed to be private. For example, a login mechanism may be listening on one network port, but after successful authentication, it may open up a second port where it waits for the connection, but avoids authentication because it assumes that only the authenticated party will connect to the port. In general, if the software or protocol allows a single session or user state to persist across multiple connections or channels, authentication and appropriate credential management need to be used throughout.
Weakness & attack patterns
- CWE-306Missing Authentication for Critical Function
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /praisonai-agents/praisonaiagents/server/server.py, /publish, /events, /info.
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 4.3 (AV:A)
Sep 14, 2026 · NVD
Initial · CVE published
Sep 14, 2026 · NVD
CVE published by MITRE.
Sep 14, 2026 · SOCRadar CTI
Added · GHSA-35w5-pcw4-jx94 published (medium)
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
- github.com/MervinPraison/PraisonAI/security/advisories/GHSA-35w5-pcw4-jx94
Exploit, Third Party Advisory
- github.com/advisories/GHSA-35w5-pcw4-jx94
Exploit, Third Party Advisory
Elsewhere on this site
- MervinPraisonevery CVE for this vendor
- pipevery CVE for this vendor
- Auth Bypasssame class
- CWE-306other 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-57128 is PraisonAI: Unauthenticated Event Injection via SSE `/publish` Endpoint, a medium 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-57128. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-57128. 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 4.3 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.