Vulnerability · Published Mar 6, 2026 · Assigned by GitHub_M

CVE-2026-30847Wekan Credential Leak via notificationUsers Publication Exposes Password Hashes and Session Tokens

Critical 9.3

In plain English

A critical-severity information exposure in Wekan from Wekan. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 19% of all known vulnerabilities).

Severity (CVSS 4.0)9.3Critical

Exploit odds (30 days)0.3%top 81.0% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

Official description

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.

Affected products (as reported)

Vendor	Product	Versions
Wekan	Wekan	>= 8.31.0, < 8.34

Weakness: CWE-200, CWE-285 · Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:H/SA:H

References

https://securitylab.github.com/advisories/GHSL-2026-035_Wekan/ x_refsource_CONFIRM
https://github.com/wekan/wekan/commit/1c8667eae8b28739e43569b612ffdb2693c6b1ce x_refsource_MISC
https://github.com/wekan/wekan/releases/tag/v8.34 x_refsource_MISC