# CVE-2026-74799: SiYuan before 3.7.4 Unauthenticated Debug Endpoint Information Disclosure

> Attackers can access unauthenticated debug endpoints to extract in-memory secrets like API keys when the application is not in production mode.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:L/SC:H/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-hmr2-j8m8-f585

## What is CVE-2026-74799?

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

### Official description

SiYuan before 3.7.4 registers Go net/http/pprof debug endpoints including heap and goroutine dumps without authentication when --mode flag is not set to exactly prod. Attackers can access /debug/pprof/heap and related endpoints to extract in-memory secrets including AccessAuthCode and AI provider API keys.

Weakness: CWE-215 (Insertion of Sensitive Information Into Debugging Code)

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


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

No fix has been published for CVE-2026-74799 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-74799 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74799 is a critical vulnerability in siyuan-note siyuan, published on 17 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-74799 exists.

Affected product: siyuan-note siyuan. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-74799/ (Markdown: https://insights.sbomify.com/CVE-2026-74799/index.md)
```

## Sources

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

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