Skip to main content
CVE-2026-40289VulnerabilityPublished Updated

Praisonaiagents: PraisonAI Browser Server allows unauthenticated WebSocket clients to hijack connected extension

Affects praisonaiagentsSource GCVE Database

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

Not known to be exploited · CVSS 9.1 Critical : upgrade to 1.5.140 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 1.5.140, 4.5.139
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 14 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 praisonaiagents to 1.5.140; PraisonAI to 4.5.139.

Affected software

ProductAffectedFixed in
PyPIpraisonaiagentsAffected
  • <1.5.140
Fixed in
  • 1.5.140
PyPIPraisonAIAffected
  • <4.5.139
Fixed in
  • 4.5.139

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 versions 1.5.140 and 4.5.139 that addresses this vulnerability. Users should upgrade to these fixed versions to remediate the issue. Until patched, restricting network exposure of the browser bridge to trusted hosts and enforcing strict Origin header validation or authentication mechanisms can mitigate the risk.

Description

PraisonAI Browser Server exposes a WebSocket endpoint that accepts unauthenticated clients without an Origin header, allowing them to hijack connected browser automation sessions. An attacker can connect remotely, initiate a session, and receive action/status streams from a connected browser extension without any credentials. This vulnerability arises from the server's trust model, which assumes WebSocket clients are local and trusted, but does not enforce authentication or strict origin checks.

References

Community reviews

Loading reviews…