CVE-2026-1964: A vulnerability was determined in WeKan up to 8.20

Q: How do I fix CVE-2026-1964?

wekan: upgrade to 8.21. Exact commands for each OS are on this page.

Q: Is CVE-2026-1964 being exploited?

CVE-2026-1964 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-1964 affect?

CVE-2026-1964 affects wekan. Severity is medium (CVSS 4.3). A vulnerability was determined in WeKan up to 8.20. This impacts an unknown function of the file models/boards.js of the component REST Endpoint. This manipulation causes improper access controls. Remote exploitation of the attack is possib

Q: How urgent is CVE-2026-1964?

Priority 19/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2026-1964 is a medium-severity flaw (CVSS 4.3) affecting wekan. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was determined in WeKan up to 8.20. This impacts an unknown function of the file models/boards.js of the component REST Endpoint. This manipulation causes improper access controls. Remote exploitation of the attack is possible. Upgrading to version 8.21 will fix this issue. Patch name: 545566f5663545d16174e0f2399f231aa693ab6e. It is advisable to upgrade the affected component.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 83%)
CISA exploited list	No
Weakness	CWE-266, CWE-284
Published	2026-02-05
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: wekan project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-05 22:15 UTCPublished CVE record published
2026-06-17 10:16 UTCUpdated Record last modified

wekan project wekan UPGRADE

Affected: < 8.21

Fixed in: 8.21

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wekan || rpm -q wekan || wekan --version

2. UPGRADE to 8.21 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wekan

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wekan

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-1964?

wekan: upgrade to 8.21. Exact commands for each OS are on this page.

Is CVE-2026-1964 being exploited?

CVE-2026-1964 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-1964 affect?

CVE-2026-1964 affects wekan. Severity is medium (CVSS 4.3). A vulnerability was determined in WeKan up to 8.20. This impacts an unknown function of the file models/boards.js of the component REST Endpoint. This manipulation causes improper access controls. Remote exploitation of the attack is possib

How urgent is CVE-2026-1964?

Priority 19/100. No elevated risk signals yet.

Related CVEs

CVE-2025-65781 HIGH 8.2 UPGRADE An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16
CVE-2025-65780 HIGH 8.8 UPGRADE An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16
CVE-2025-65779 HIGH 7.5 UPGRADE An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16
CVE-2025-65778 HIGH 8.1 UPGRADE An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16
CVE-2025-65782 MEDIUM 6.5 UPGRADE An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16

References

← Back to latest CVEs