CVE-2026-52890 wekan CVE debrief

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.

Official resources