CVE-2026-42889: No-Instructions relay-server · Incorrect Authorization
Affects No-Instructions relay-serverSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.9.7 as a priority.
Data as of 18 Nov 2026, 20:25 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.9.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 18 Nov 2026.
What to do
Upgrade relay-server and no-instructions/relay-server to 0.9.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| No-Instructionsrelay-server | Affected
| Fixed in
|
GitHubno-instructions/relay-serverpkg:github/no-instructions/relay-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in No-Instructions relay-server version 0.9.7. Users should upgrade to version 0.9.7 or later to remediate this issue. Patch status is not explicitly stated in the vendor advisory content provided, but the description confirms the fix in 0.9.7. Until upgraded, restrict network access to the relay-server WebSocket endpoints to trusted users only.
Description
Relay adds real-time collaboration to Obsidian. Relay Server versions 0.9.0 through 0.9.6 contain an authentication bypass in the multi-document WebSocket endpoints. When authentication is configured, WebSocket connections without a token query parameter were incorrectly treated as having full server permissions. An unauthenticated network attacker who knows or guesses a document ID could connect to the document sync WebSocket and read or modify document contents without a valid document token. This vulnerability is fixed in 0.9.7.