CVE-2026-66013CVSS 9.8 Critical2026-07-25
OpenRemote Console Registration API Authorization Bypass Leading to Notification Redirection
In OpenRemote prior to version 1.26.2, the console registration API lacks ownership verification, resulting in authorization bypass through a user-controlled key (CWE-639). An attacker who supplies a known asset identifier can update an existing console asset without authentication. The attacker can overwrite push notification tokens and console metadata, thereby redirecting notifications or preventing legitimate consoles from receiving them. The vulnerability affects all OpenRemote users who have not updated to 1.26.2. An attacker only needs to know an asset identifier to exploit it remotely, requiring no authentication while being able to tamper with critical communication data.
Component
OpenRemote is an open-source Internet of Things (IoT) platform used to connect, monitor and control devices and assets, supporting asset management and notification delivery through a console.
Risks
- Notification hijacking and redirection: An attacker can overwrite push notification tokens and redirect sensitive notifications intended for legitimate consoles to attacker-controlled devices
- Denial of service: An attacker can tamper with console metadata so that legitimate consoles no longer receive notifications, creating monitoring blind spots or business disruption
- Unauthenticated data tampering: An attacker can modify critical asset configuration without any credentials, undermining the integrity of system data
Source
Remediation- Immediately upgrade OpenRemote to version 1.26.2 or later
- Monitor logs for anomalous changes to console asset metadata and notification tokens
- Apply network-layer access control to restrict the sources permitted to reach the console registration API
CVE-2026-66012CVSS 10.0 Critical2026-07-25
SiYuan MCP Endpoint Missing Authorization Leading to Administrator Takeover
In SiYuan versions prior to v3.7.2, the POST /mcp kernel endpoint contains a missing authorization (CWE-862) security flaw. The endpoint is protected only by a generic authentication check, without enforced restrictions for administrator roles or read-only permissions, exposing 31 MCP tools including file operations. When the publishing server is enabled in anonymous mode, a remote unauthenticated attacker can use the anonymous JWT attached to proxied requests to reach the endpoint, read sensitive configuration files, write arbitrary files and plant malicious plugins, ultimately achieving administrator takeover. The vulnerability affects all SiYuan users who have not updated to v3.7.2, particularly deployments with anonymous publishing enabled. An attacker can exploit it remotely without user interaction and obtain the highest level of system control.
Component
SiYuan is a local-first, privacy-first personal knowledge management application supporting Markdown and block-level references, providing note taking, document management and plugin extension capabilities.
Risks
- Sensitive information disclosure: An attacker can read conf/conf.json and extract critical credentials such as accessAuthCode, api.token and cookieKey in plaintext
- Arbitrary file read and write: An attacker can perform list/read/write/delete/rename/copy operations across the entire workspace, damaging data integrity or planting backdoors
- Administrator takeover: By planting a malicious plugin that executes with nodeIntegration:true and without contextIsolation, an attacker can gain administrator privileges when the desktop client starts
- Unauthenticated remote attack: In anonymous publishing mode, an attacker can reach the protected endpoint directly without credentials and achieve remote code execution
Source
Remediation- Immediately upgrade SiYuan to v3.7.2 or later to fix the authorization logic flaw
- Avoid enabling anonymous publishing mode in production (Conf.Publish.Auth.Enable=false)
- Regularly monitor the data/plugins/ and conf/ directories for anomalous file changes
- Apply network access control to the SiYuan service and restrict source IPs allowed to reach the /mcp endpoint