Skip to main content
VulnerabilityPublished Updated

CVE-2026-34952: PraisonAI Has Missing Authentication

Affects praisonaiSource GCVE Database

0
Compare
Authoritative record:CVE-2026-34952· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.5.97 as a priority.

Data as of 16 Nov 2026, 16:37 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.5.97
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade praisonai to 4.5.97.

Affected software

ProductAffectedFixed in
PyPIpraisonaiAffected
  • <4.5.97
Fixed in
  • 4.5.97

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in PraisonAI version 4.5.97 that enforces authentication on WebSocket connections by validating a token from query parameters or Authorization headers against the configured auth_token. Users should upgrade to version 4.5.97 or later to remediate this vulnerability. Until upgraded, no other vendor-provided mitigations are indicated.

Description

PraisonAI Gateway server versions prior to 4.5.97 have a missing authentication vulnerability in their WebSocket gateway. The server accepts WebSocket connections at /ws and provides agent topology information at /info without requiring authentication. This allows any network client to enumerate registered agents and send arbitrary messages to them, potentially executing tools, reading files, and making API calls. The vulnerability is due to the GatewayConfig's auth_token not being enforced in the WebSocket handler. A fix is available in version 4.5.97 that adds token-based authentication to the WebSocket endpoint.

References

Community reviews

Loading reviews…