Skip to main content
CVE-2026-2205VulnerabilityPublished Updated

CVE-2026-2205: WeKan · Information Disclosure

Affects WeKanSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
WeKanAffected
  • =8.0
  • =8.1
  • =8.2
  • =8.3
  • =8.4
  • =8.5
  • =8.6
  • =8.7
  • =8.8
  • =8.9
  • =8.10
  • =8.11
  • =8.12
  • =8.13
  • =8.14
  • =8.15
  • =8.16
  • =8.17
  • =8.18
  • =8.19
  • =8.20
Fixed in–
GitHubwekan/wekanpkg:github/wekan/wekanOther threatsAffected
  • =8.0
  • =8.1
  • =8.2
  • =8.3
  • =8.4
  • =8.5
  • =8.6
  • =8.7
  • =8.8
  • =8.9
  • =8.10
  • =8.11
  • =8.12
  • =8.13
  • =8.14
  • =8.15
  • =8.16
  • =8.17
  • =8.18
  • =8.19
  • =8.20
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-2205, organizations should immediately upgrade all affected WeKan instances to version 8.21 or later, which contains the official patch (commit 0f5a9c38778ca550cbab6c5093470e1e90cb837f) addressing the vulnerability. In addition to patching, administrators should restrict network access to WeKan servers by implementing firewall rules or VPN access to limit exposure to trusted users only. Conduct a thorough audit of current WeKan deployments to identify any publicly accessible instances and apply access controls accordingly. Monitor logs for unusual access patterns or data requests that could indicate exploitation attempts. If upgrading is temporarily not possible, consider disabling or restricting the Meteor Publication Handler component or the affected publications, if feasible, to reduce exposure. Regularly review and update user permissions within WeKan to enforce the principle of least privilege. Finally, maintain an incident response plan to quickly address any suspected data disclosure incidents related to this vulnerability.

Description

A vulnerability was identified in WeKan up to 8.20. This affects an unknown part of the file server/publications/cards.js of the component Meteor Publication Handler. Such manipulation leads to information disclosure. The attack may be performed from remote. Upgrading to version 8.21 is able to mitigate this issue. The name of the patch is 0f5a9c38778ca550cbab6c5093470e1e90cb837f. Upgrading the affected component is advised.

References

Community reviews

Loading reviews…