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

> Authenticated users can harvest password hashes and session tokens from other users due to unfiltered data publication, enabling account takeover.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2026
- **Updated:** 9 Mar 2026

## What is CVE-2026-30847?

CVE-2026-30847 is a critical vulnerability in Wekan, published on 6 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### 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.

Weakness: CWE-285 (Improper Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-30847?

It affects 1 product.


Products: Wekan Project Wekan.

## How do I fix CVE-2026-30847?

No fix has been published for CVE-2026-30847 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-30847 being exploited?

There is no known exploitation of CVE-2026-30847 in the wild and no public exploit code.

## Other vulnerabilities in Wekan

- [CVE-2026-30843](https://insights.sbomify.com/CVE-2026-30843/): Wekan has Cross-Board IDOR in Custom Fields Update Endpoints (critical 9.3)
- [CVE-2026-30844](https://insights.sbomify.com/CVE-2026-30844/): Wekan Vulnerable to SSRF through Lack of Validation or Filtering in Attachment URL Loading (critical 9.3)
- [CVE-2025-65780](https://insights.sbomify.com/CVE-2025-65780/): Missing authorization in n/a (high 8.8)
- [CVE-2026-30846](https://insights.sbomify.com/CVE-2026-30846/): Wekan Exposes All Global Webhook Integrations through globalwebhooks Publication (high 8.7)
- [CVE-2026-25560](https://insights.sbomify.com/CVE-2026-25560/): WeKan < 8.19 LDAP Authentication Filter Injection (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30847 and fix it if it is affected.

What it is: CVE-2026-30847 is a critical vulnerability in Wekan, published on 6 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-30847 in the wild and no public exploit code.

Affected product: Wekan. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30847/ (Markdown: https://insights.sbomify.com/CVE-2026-30847/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30847
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30847
- OSV: https://osv.dev/vulnerability/CVE-2026-30847

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30847/
Summaries are generated and may contain mistakes; the official description above is the record.