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

New CVE Detected

CVE-2026-73046 – Authentication Bypass / Brute-Force via HTTP Basic Auth – SiYuan Note before v3.7.4

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

Summary

CVE-2026-73046 is an authentication bypass vulnerability in SiYuan Note affecting the kernel’s CheckAuth() middleware, which guards nearly the entire /api/* surface. Versions before 3.7.4 accept the workspace access code as an HTTP Basic Authentication password without ever consulting the CAPTCHA/lockout gate or incrementing the failure counter used by the normal cookie/session login path, allowing unlimited automated brute-force attempts. Successful exploitation grants an unauthenticated remote attacker full RoleAdministrator access to the kernel; the CVE carries a critical severity rating.

Technical details

  • Root cause: The HTTP Basic Auth branch of CheckAuth() validates the supplied password against Conf.AccessAuthCode but bypasses the rate-limiting/lockout logic applied to the cookie/session login flow, so failed attempts are never throttled or counted.
  • Secondary weakness: The access code comparison is not constant-time, which can aid attackers attempting to infer correctness of guesses through timing differences.
  • Trigger conditions: The target must be reachable over the network with its /api/* endpoints exposed and Basic Authentication enabled/accepted.
  • Attack vector: Network — no authentication or user interaction required; an attacker simply sends repeated HTTP Basic Auth requests against the exposed API.
  • Impact: Full administrator takeover of the SiYuan kernel, with complete loss of confidentiality, integrity, and availability of workspace data and functionality.

Affected software

  • SiYuan (kernel component, github.com/siyuan-note/siyuan/kernel) — all versions prior to 3.7.4
  • Fixed in version 3.7.4 and later

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 Base Score: 9.3 (Critical)CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade SiYuan to version 3.7.4 or later, where proper CAPTCHA/lockout enforcement and failure-counter tracking are applied to the HTTP Basic Authentication path.
  • If unable to patch immediately: Do not expose the SiYuan kernel API directly to the internet; restrict access via a firewall, VPN, or reverse proxy that enforces its own authentication and rate limiting, and rotate the workspace access code after remediation.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Access Authorization - SiYuan, 思源笔记
  • Raw response body: exitSiYuan, b3log.org/siyuan

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