External risk intelligence

Siyuan Session Cookie Signing Key Disclosure in Publish Mode.

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-72794

The vulnerability exists in a web application feature (publish mode) that is designed to be accessible over the network. Because the application exposes an API endpoint intended for interaction in a public or shared context, it is commonly deployed in an internet-facing capacity.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in SiYuan that allows unauthenticated access to sensitive session cookie information. This exposure could enable unauthorized users to impersonate legitimate users or gain administrative control over the system.

Unauthenticated access to session key.
Matters for unauthorized user impersonation.
Confirm relevance and potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker can access an exposed configuration endpoint on a server running Siyuan in publish mode. This endpoint, `/api/system/getConf`, leaks a secret value, the session cookie signing key. An attacker can then use this key to forge session cookies, allowing them to impersonate any user, including administrators, and gain unauthorized access.

Unauthenticated access to specific endpoint.
Retrieves session cookie signing key.
Impersonate users or gain admin access.

Live Threat

Current exploitation, exposure, and threat context

In publish mode, an unauthenticated attacker could retrieve the session cookie signing key from the `/api/system/getConf` endpoint. This could allow an attacker to forge session cookies and impersonate users or gain administrative access to the system.

User session cookies and administrative access.
Unauthenticated access to an API endpoint.
Unauthorized user impersonation or administrative control.

Operational Fix

Recommended remediation, mitigation, and detection steps

Teams responsible for SiYuan instances, likely application owners or infrastructure teams, must first identify all deployments. Confirming which instances are exposed externally and deemed business-critical will prioritize efforts. Subsequently, the accountable owner should be identified to coordinate a risk-based remediation plan, which may involve vendor coordination and maintenance window scheduling.

Application or infrastructure teams own remediation.
Verify external exposure and business criticality.
Plan vendor coordination and maintenance.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Siyuan?

Siyuan is a privacy-first, local-first personal knowledge management software. It allows users to manage notes and documents, often supporting features like local hosting or sharing content via a publish mode, which can be configured to make certain data accessible over a network.

What does CVE-2026-72794 mean for security?

This vulnerability relates to CWE-522, which involves insufficient protection of credentials. In this specific case, the software unintentionally shares a secret signing key used for session cookies. By obtaining this key, an unauthorized party can bypass authentication and potentially pretend to be any user, including an administrator.

How is this vulnerability triggered?

An attacker can trigger this by sending a request to the /api/system/getConf endpoint while the software is running in publish mode. The bug does not trigger if publish mode is disabled or if the instance is not reachable by the attacker; the vulnerability specifically relies on the ability of an unauthenticated user to access that specific configuration path.

Is my Siyuan instance at risk?

According to Halo Surface Signal, this risk is higher if your Siyuan instance is internet-facing. Because publish mode is designed to make information accessible over a network, instances deployed in public or shared contexts are more likely to be reachable by unauthorized parties, increasing the potential for successful exploitation of the signing key disclosure.

How should I respond to this vulnerability?

Your first step is to locate all Siyuan deployments within your environment. Once identified, determine if they are currently running in publish mode and whether they are exposed to the internet. If so, prioritize these for updates to version 3.7.4 or later, coordinating with your internal teams to schedule the necessary maintenance.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.