CVE-2026-30847: GHSL-2026-035: Wekan may Leak Credentials During User Notification Workflow - CVE-2026-30847
Wekan is an open source kanban tool built with Meteor. In versions 8.31.0 through 8.33, the notificationUsers publication in Wekan publishes user documents with no field filtering, causing the ReactiveCache.getUsers() call to return all fields including highly sensitive data such as bcrypt password hashes, active session login tokens, email verification tokens, full email addresses, and any stored OAuth tokens. Unlike Meteor's default auto-publication which strips the services field for security, custom publications return whatever fields the cursor contains, meaning all subscribers receive the complete user documents. Any authenticated user who triggers this publication can harvest credentials and active session tokens for other users, enabling password cracking, session hijacking, and full account takeover. This issue has been fixed in version 8.34.
Other sources
Wekan v8.31.0 is vulnerable to a credential leakage issue (GHSL-2026-035), where sensitive user credentials could be exposed through the notificationUsers publication, potentially leading to unauthorized access and data compromise.
— GitHub Security Lab
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-30847?
CVE-2026-30847 is considered a high-severity vulnerability due to the exposure of sensitive user credentials.
How do I fix CVE-2026-30847?
To fix CVE-2026-30847, upgrade Wekan to version 8.34 or later where the vulnerability has been addressed.
What versions of Wekan are affected by CVE-2026-30847?
CVE-2026-30847 affects Wekan versions 8.31.0 through 8.33.
What type of data is exposed due to CVE-2026-30847?
CVE-2026-30847 exposes password hashes and session tokens of users due to a lack of field filtering.
Is a workaround available for CVE-2026-30847?
There is no documented workaround for CVE-2026-30847; the recommended action is to upgrade to the fixed version.