Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-74799 – Sensitive Credential Disclosure via Unauthenticated pprof Debug Endpoints – SiYuan

Be the first to know when new zero-days emerge:

Summary

CVE-2026-74799 is a critical information disclosure vulnerability in SiYuan Note, a self-hosted personal knowledge management application. When SiYuan’s kernel is started with the --mode flag set to any value other than prod, its serveDebug() function registers Go’s built-in net/http/pprof debugging endpoints without any authentication. A remote, unauthenticated attacker can query these endpoints over the network to dump process memory, potentially recovering sensitive secrets such as the workspace access authorization code and configured AI provider API keys. The flaw affects all SiYuan versions before 3.7.4 and carries a CVSS score of 9.2–9.3 (Critical).

Technical details

  • Root cause: The SiYuan kernel’s debug-server initialization registers Go net/http/pprof handlers (e.g., /debug/pprof/heap, /debug/pprof/goroutine) without any authentication middleware.
  • Trigger conditions: The endpoints are exposed whenever the kernel is launched with --mode not explicitly set to prod (e.g., left at a default/dev mode), which can occur in real-world deployments that do not set this flag.
  • Attack vector: Network-based, requires no authentication and no user interaction (AV:N/AC:L/PR:N/UI:N).
  • Impact: An attacker can retrieve heap and goroutine memory dumps, exposing in-memory secrets including the SiYuan access authorization code and AI provider API keys, enabling full account/workspace takeover or downstream API abuse.

Affected software

  • SiYuan (siyuan-note/siyuan), Go kernel package github.com/siyuan-note/siyuan/kernel
  • All versions 3.7.3 and earlier, when run without --mode=prod
  • Fixed in version 3.7.4

Severity

  • CVSS v3.1 Base Score: 9.3 (Critical)
  • CVSS v3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

Mitigation and recommended actions

  • Immediate: Upgrade SiYuan to version 3.7.4 or later, which removes/secures the unauthenticated pprof debug endpoints.
  • If immediate patching is not possible: Ensure the kernel is always started with --mode=prod in any deployment reachable from a network; do not expose the SiYuan kernel port directly to the internet; place it behind a reverse proxy or firewall that blocks access to /debug/pprof/* paths; rotate the workspace access authorization code and any AI provider API keys configured in the application after remediation, as they may have been exposed.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge