PatchSiren cyber security CVE debrief
CVE-2026-52890 wekan CVE debrief
CVE-2026-52890 is a high-severity vulnerability in Wekan, a Meteor-based open-source kanban platform. It allows logged-in board members to insert attachments, potentially leading to arbitrary file reads and denial of service through special files like /dev/zero. The issue is fixed in version 9.31. Affected product deployments should be identified, and owners assigned for follow-up. The vulnerability exists due to insufficient checks in the /attachments/insert DDP method and FileStoreStrategyFilesystem.getReadStream() in models/lib/fileStoreStrategy.js.
- Vendor
- wekan
- Product
- Unknown
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-15
- Original CVE updated
- 2026-07-16
- Advisory published
- 2026-07-15
- Advisory updated
- 2026-07-16
Who should care
Users of Wekan kanban platform, especially those with logged-in board members, should be aware of this vulnerability and take immediate action to update to version 9.31 or apply necessary patches. Affected operators, platform administrators, vulnerability management teams, and security teams should review the vulnerability and implement necessary mitigations.
Technical summary
The vulnerability exists in the /attachments/insert DDP method, where the server/permissions/attachments.js insert rule only checks for board write access. Additionally, FileStoreStrategyFilesystem.getReadStream() in models/lib/fileStoreStrategy.js streams the stored path without a storage-root containment check, allowing arbitrary file reads and potential denial of service. The issue can be mitigated by updating to version 9.31 or applying necessary patches.
Defensive priority
High priority should be given to updating Wekan to version 9.31 or applying necessary patches to prevent exploitation of this vulnerability. Additional monitoring and logging should be implemented to detect potential exploitation attempts.
Recommended defensive actions
- Update Wekan to version 9.31 or later
- Restrict access to the /attachments/insert DDP method
- Implement additional monitoring and logging to detect potential exploitation attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record was published on 2026-07-15T22:17:16.310Z and last modified on 2026-07-16T14:16:53.827Z. The NVD entry is currently Deferred. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the vendor. The issue is fixed in version 9.31 of Wekan. Evidence limits and unknown affected scope should be considered during review.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-52890 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-52890
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-52890 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-52890
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/wekan/wekan/commit/fc92b342ceedcf38dbd614a0f7b50d6dc2b22eb8
-
Source reference
Unverified legacy reference
URL: https://github.com/wekan/wekan/releases/tag/v9.31
-
Source reference
Unverified legacy reference
URL: https://github.com/wekan/wekan/security/advisories/GHSA-g6vm-7757-pr88
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.