External risk intelligence

Relay Server lets attackers steal or change shared documents without login

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-42889

Relay Server versions 0.9.0-0.9.6 have a critical flaw allowing anyone to read or change shared documents without a password. This impacts real-time collaboration by letting attackers access sensitive content over the network.

4Halo Surface Signal

Authentication Bypass

External exposure likelihood

Halo Surface Signal score for CVE-2026-42889

The Relay Server is a real-time collaboration service providing WebSocket endpoints for document synchronization. Such services are commonly deployed as network-accessible web applications or APIs to facilitate remote document sharing, making them likely candidates for exposure to the public internet or broad internal network segments to support collaboration workflows.

Horizon Alert

Summary of the vulnerability and why it matters

The Relay Server has an authentication bypass flaw that could allow unauthorized access to documents. This is concerning because it means someone could potentially read or change your team's shared content without permission.

  • Unauthenticated access to documents.
  • Can read or modify document contents.
  • Affects real-time collaboration features.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker could exploit this by connecting to a Relay server's WebSocket endpoint and manipulating document content if they can guess a document ID. This bypasses the need for any valid authentication or authorization.

  • Network access required.
  • Target document sync WebSocket.
  • Guess document ID.

Live Threat

Current exploitation, exposure, and threat context

The current threat picture indicates a significant risk due to an authentication bypass vulnerability in Relay Server. Attackers can exploit this to gain unauthorized access to real-time collaborative documents, potentially leading to data compromise. The vulnerability is exploitable over the network without requiring user interaction or prior privileges.

  • Exploitable without authentication.
  • Real-time collaboration services targeted.
  • Fix available in 0.9.7.

Priority actions

Operational Fix

Recommended remediation, mitigation, and detection steps

Prioritize patching Relay Server to version 0.9.7 to address the authentication bypass vulnerability. If patching is delayed, implement network segmentation to isolate affected servers and strictly monitor for unauthorized WebSocket connections on document sync endpoints.

  • Apply patch 0.9.7 immediately.
  • Block unauthenticated WebSocket connections.
  • Monitor WebSocket traffic for anomalies.

Frequently asked questions

What is the Relay Server and its function in real-time collaboration?

Relay Server enhances Obsidian by enabling real-time collaboration features. It facilitates document synchronization through WebSocket endpoints, allowing multiple users to work on documents simultaneously.

What type of vulnerability does Relay Server versions 0.9.0 through 0.9.6 have?

These Relay Server versions contain an authentication bypass vulnerability in their multi-document WebSocket endpoints.

How can an attacker exploit the authentication bypass in Relay Server?

An unauthenticated attacker can exploit this by connecting to the document sync WebSocket without a token query parameter. If the attacker can guess or know a document ID, they can read or modify document contents without proper authorization.

What is the relevance of this vulnerability to connected systems?

This vulnerability is relevant because it allows unauthenticated network attackers to bypass security controls and access or alter sensitive document content in real-time collaboration sessions. The Relay Server is likely deployed as a network-accessible application, increasing its exposure.

What is the recommended action to mitigate this vulnerability?

The recommended action is to update Relay Server to version 0.9.7, which includes a fix for this vulnerability. If immediate patching is not possible, consider network segmentation to isolate affected servers and monitor WebSocket traffic for suspicious activity.

References