CVE-2026-55536: Browser Server WebSocket origin validation bypass via unanchored regex (patch bypass of CVE-2026-40289 / GHSA-8x8f-54wf-vv92)
PraisonAI is a multi-agent teams system. Prior to praisonai 4.6.58, Browser Server _handle_connection() checks Chrome extension origins with re.match() and the unanchored expression chrome-extension://[a-z0-9]{32}. Extra trailing characters pass before websocket.accept(), allowing start_session commands and unauthorized browser automation. This issue is fixed in version 4.6.58.
Security readout for executives and security teams
Plain-English summary
PraisonAI versions before 4.6.58 can mistake a crafted WebSocket origin for a trusted Chrome extension. An unauthenticated remote party could then initiate browser sessions and automate the browser, threatening the confidentiality and integrity of accessible information and actions.
Executive priority
Prioritize immediate remediation where Browser Server is reachable or controls authenticated browsers. Upgrade promptly and investigate suspicious sessions. Less-exposed installations still require scheduled remediation because exploitation needs no account or user interaction, although active attacks are not established by the supplied evidence.
Technical view
Browser Server `_handle_connection()` used `re.match()` with an unanchored Chrome-extension origin pattern. Origins beginning with the expected 32-character identifier but containing trailing characters passed validation before WebSocket acceptance, enabling unauthorized `start_session` commands. This bypasses the earlier CVE-2026-40289 fix and is corrected in 4.6.58.
Likely exposure
Exposure requires PraisonAI earlier than 4.6.58 with Browser Server functionality active and its WebSocket endpoint reachable by an attacker. Risk is greatest where automated browser sessions can access authenticated applications or sensitive information. The supplied sources do not identify affected deployment counts.
Exploitation context
The CVSS 9.1 assessment describes network exploitation with low complexity, no privileges, and no user interaction. However, the supplied record is not in KEV and provides no evidence of active exploitation. Treat exploitation status as unconfirmed rather than absent.
Researcher notes
This is an authorization failure caused by incomplete origin-string validation, categorized as CWE-284 and CWE-625. The critical boundary is validation before `websocket.accept()`. Assessment should focus on exact-match enforcement, alternate malformed origins, endpoint reachability, and whether unauthorized sessions could inherit sensitive browser state.
Mitigation direction
Upgrade PraisonAI to version 4.6.58 or later.
Restrict Browser Server WebSocket access to trusted networks and clients until upgrading.
Review vendor guidance for any additional deployment-specific safeguards.
Rotate exposed credentials or sessions if logs indicate unauthorized browser automation.
Validation and detection
Inventory PraisonAI versions and identify installations earlier than 4.6.58.
Confirm whether Browser Server and its WebSocket endpoint are enabled and network-reachable.
Verify the installed code enforces complete origin matching without accepting trailing characters.
Review WebSocket and application logs for unexpected origins, connections, or browser-session starts.
Confirm version 4.6.58 or later after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.