Service degradation via unbounded path mutex retention
Published Sep 4, 2026 · Updated Sep 4, 2026
Uncontrolled resource consumption in SiYuan before 3.8.2 allows remote attackers to degrade availability via unique request paths. The model.ControlConcurrency middleware inserts a mutex into the global requesting map for each new path before routing, but never evicts it after completion. No authentication or valid route is required; repeated unique 404 paths permanently grow process state, increasing memory pressure and synchronization overhead without reading or writing workspace data.
Summary
What happened
Uncontrolled resource consumption in SiYuan before 3.8.2 allows remote attackers to degrade availability via unique request paths. The model.ControlConcurrency middleware inserts a mutex into the global requesting map for each new path before routing, but never evicts it after completion. No authentication or valid route is required; repeated unique 404 paths permanently grow process state, increasing memory pressure and synchronization overhead without reading or writing workspace data.
The record
- CVE
- CVE-2026-85585
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- Vendor
- SiYuan Note
- Product
- SiYuan
- Classifications
- CWE-400, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.8.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- ControlConcurrency retained-entry reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo