CVE-2026-30847
- Source
- https://cve.org/CVERecord?id=CVE-2026-30847
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-30847.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-30847
- Published
- 2026-03-06T19:37:19.337Z
- Modified
- 2026-04-02T13:23:17.422385Z
- Severity
-
- 9.3 (Critical) CVSS_V4 - 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 CVSS Calculator
- Summary
- Wekan Credential Leak via notificationUsers Publication Exposes Password Hashes and Session Tokens
- Details
-
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.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/30xxx/CVE-2026-30847.json", "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-200", "CWE-285" ] }- References
-
- https://github.com/wekan/wekan/releases/tag/v8.34
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/30xxx/CVE-2026-30847.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-30847
- https://securitylab.github.com/advisories/GHSL-2026-035_Wekan/
- https://github.com/wekan/wekan/commit/1c8667eae8b28739e43569b612ffdb2693c6b1ce