SiYuan kernel versions before 3.7.4 contain an improper restriction of excessive authentication attempts vulnerability in the CheckAuth() middleware. The middleware accepts the API token (Conf.Api.Token) via an Authorization header (Token/Bearer) or a ?token= query parameter, and neither path is protected by the application's CAPTCHA/lockout mechanism (NeedCaptcha/WrongAuthCount). As a result, an unauthenticated remote attacker can perform unlimited automated guesses of the API token, particularly when a short or weak custom token has been configured, and upon success gains full RoleAdministrator access enabling arbitrary file operations and SQL queries.
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
SiYuan kernel versions before 3.7.4 suffer from an improper restriction of excessive authentication attempts vulnerability (CWE-307) in the CheckAuth() middleware. The flaw allows unauthenticated remote attackers to bypass rate-limiting and CAPTCHA protections when attempting to guess API tokens submitted via Authorization headers or query parameters. This critical vulnerability (CVSS 9.8) affects any organization running vulnerable SiYuan instances, as attackers can conduct unlimited automated brute-force attacks against the API token without triggering account lockouts or challenge mechanisms. Once an attacker obtains a valid token, they gain full API access to the application, potentially enabling data exfiltration, system manipulation, or lateral movement within the infrastructure.
Casky's Claude-powered analysis engine would identify this attack pattern through behavioral anomaly detection across authentication logs, flagging high-volume failed authentication attempts from single or distributed sources targeting the token endpoint. Practitioners would observe findings related to Credential Access techniques—specifically Brute Force attacks—with extended reasoning revealing the absence of expected rate-limiting responses and CAPTCHA triggers despite repeated failed attempts. The platform would correlate suspicious query parameters (?token=) and Authorization headers with failed authentication sequences, allowing security teams to rapidly distinguish legitimate API usage from exploitation attempts and implement compensating controls or upgrade to patched versions before tokens are compromised.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-73056. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation