# CVE-2026-72794: siyuan before v3.7.4 Session Cookie Key Disclosure via getConf

> Unauthenticated attackers can retrieve the session cookie signing key in publish mode to forge cookies and impersonate users or gain admin access.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-34fj-mwm6-fjfg, GO-2026-6420

## What is CVE-2026-72794?

CVE-2026-72794 is a critical vulnerability in siyuan-note siyuan, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

siyuan versions before v3.7.4 expose the session cookie signing key through the /api/system/getConf endpoint to unauthenticated users in publish mode. Attackers can retrieve the CookieKey value and forge valid session cookies to impersonate users or gain administrative access.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-72794?

3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260725123945-77421530be4a |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260725123945-77421530be4a |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260725123945-77421530be4a |

## How do I fix CVE-2026-72794?

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260725123945-77421530be4a or later.

## Is CVE-2026-72794 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72794 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72794 and fix it if it is affected.

What it is: CVE-2026-72794 is a critical vulnerability in siyuan-note siyuan, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72794 exists.

Affected packages and fixed versions:
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260725123945-77421530be4a
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260725123945-77421530be4a
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260725123945-77421530be4a

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72794/ (Markdown: https://insights.sbomify.com/CVE-2026-72794/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72794
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72794
- OSV: https://osv.dev/vulnerability/CVE-2026-72794

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72794/
Summaries are generated and may contain mistakes; the official description above is the record.