CVE-2026-55234
Auth users can move cards/lists into private Wekan boards bypassing membership.
Is CVE-2026-55234 being exploited?
Not confirmed. CVE-2026-55234 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-55234?
CVE-2026-55234 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-55234?
Yes. A fix has been recorded for CVE-2026-55234. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-55234 affect?
CVE-2026-55234 affects Wekan < 9.37, Self-hosted Wekan servers, Docker/hosted Wekan deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-55234?
Upgrade to Wekan 9.37+, restrict board write rights and audit board activity
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated users with write on their board can relocate cards/lists/swimlanes into private boards they don't belong to, enabling unauthorized data manipulation and potential data exposure.
Patch when possible
- affected< 9.37
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.