Wekan is open source kanban built with Meteor. Prior to 9.31, Wekan allows a logged-in board member to insert an attachment document through the /attachments/insert DDP method with attacker-controlled versions.original.path and versions.original.storage fields. The server/permissions/attachments.js insert rule checks only board write access, and FileStoreStrategyFilesystem.getReadStream() in models/lib/fileStoreStrategy.js streams the stored path without a storage-root containment check, allowing arbitrary file reads and denial of service through special files such as /dev/zero. This issue is fixed in version 9.31.
CVE-2026-52890
This high-severity CVE scores 7.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(low)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026Arbitrary file read and server DoS via attachment versions.original.path · Advisory · wekan/wekan · GitHub
https://github.com/wekan/wekan/security/advisories/GHSA-g6vm-7757-pr88v9.31
Patch available: wekan/wekan v9.31
https://github.com/wekan/wekan/releases/tag/v9.31commit fc92b342ceed (wekan/wekan)
Fix landed in wekan/wekan commit fc92b342ceed — awaiting tagged release
https://github.com/wekan/wekan/commit/fc92b342ceedcf38dbd614a0f7b50d6dc2b22eb8Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 21:24 UTCEG score recompute
- 2026-07-15 21:23 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-22 · CWE-400
- CVE-2004-0847EG 9.8EPSS 99%CRITICAL
- CVE-2004-1464NVD 5.9EG 9.0 KEVEPSS 91%MEDIUM
- CVE-2001-0925NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2002-20001EG 7.5EPSS 97%HIGH
- CVE-2005-2349EG 7.5HIGH
- CVE-2006-5708EG 7.5HIGH
- CVE-2006-1364EG 7.5EPSS 99%HIGH
- CVE-2001-0827EG 7.5HIGH
- CVE-2005-10002EG 5.5MEDIUM
- CVE-2006-5648EG 5.5MEDIUM
Frequently asked(4)
What is CVE-2026-52890?
When was CVE-2026-52890 disclosed?
What is the CVSS score of CVE-2026-52890?
How do I remediate CVE-2026-52890?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-52890
Is Your Infrastructure Affected by CVE-2026-52890?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.