Skip to main content
Menu
CVEs

CVE

SiYuan captcha bypass in login enables access code brute-force

Affects SiYuan 2.1.0 before 3.8.9 workspaces that use the public kernel access-code login. CVSS rates it critical (9.1). Fixed in 3.8.9.

CVE-2026-126265EUVD-2026-125256GHSA-23G4-VQQ8-5764GHSA-GFVP-WQXW-G8QP

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

9.1CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 3.8.9
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.8.9.

Published
Last modified
Reference
Last checked
0.29% · 21st percentile
36/100
Unclear
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post

Summary

SiYuan 2.1.0 before 3.8.9 contains a flaw where the loginAuth CAPTCHA challenge lives in a signed client-side cookie, allowing reuse of a solved challenge. Attackers can replay the original signed siyuan cookie with distinct wrong access codes to brute-force the code and gain an administrator session.

Who should check

Teams running SiYuan 2.1.0 before 3.8.9 with access-code login enabled, and anyone building on the siyuan kernel Go package

“Affecting siyuan >= 2.1.0, < 3.8.9”

vulncheck.com

cve.now Index

36cve.now Index 36 of 100 · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach10/20Affects Go packages
  • Severity9.1/10CVSS 9.1
  • No patch0/5No signal

What would change the score

  • Would score about 81 if added to CISA KEV
  • Would score about 76 if CISA's SSVC rates exploitation active
  • Would score about 41 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 3.8.9.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126265 (SiYuan 2.1.0 before 3.8.9 CAPTCHA Bypass via Stale Login Cookie), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126265 (entry last updated 2026-11-13):
Affected:
- Go package github.com/siyuan-note/siyuan/kernel: from 2.1.0, fixed in 3.8.9
Fixed versions: 3.8.9.
Conditions (all must be true for the bug to be hit):
- Workspace uses the public kernel access-code login, which requires a CAPTCHA after four wrong codes (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-23g4-vqq8-5764)
- Attacker must make four failed login attempts first to obtain a CAPTCHA challenge (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-23g4-vqq8-5764)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126265 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126265 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-23g4-vqq8-5764
- https://www.vulncheck.com/advisories/siyuan-2.1.0-before-3.8.9-captcha-bypass-via-stale-login-cookie
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126265
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126265"}.

Public exploit activity

100%0Posted on X by cve.nowNov 13Nov 17
  • EPSS: 0.29%
  • Posted on X by cve.now Nov 13

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126265

Is CVE-2026-126265 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The CAPTCHA that the public kernel access-code login normally requires after four wrong codes can be bypassed, so an unauthenticated remote attacker can keep guessing the access code. A correct guess creates an administrator session with access to protected workspace data and administrative APIs.Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-126265?

github.com/siyuan-note/siyuan/kernel (Go): from 2.1.0 before 3.8.9.Source: cve.now feed data

Am I affected, and how do I check?

Versions from 2.1.0 up to but not including 3.8.9 are affected, and the bug applies to workspaces that use the public kernel access-code login. To check, look at the SiYuan version in the app and whether the workspace uses the kernel access-code login.Source: github.com, vulncheck.com

How do I fix CVE-2026-126265?

Upgrade to SiYuan 3.8.9 or later, which is the fixed version named in the advisory. No workaround is listed.Source: github.com, vulncheck.com