# CVE-2026-52890: Wekan: Arbitrary file read and server DoS via attachment versions.original.path

> A logged-in user can read arbitrary files or cause denial of service by manipulating attachment paths in Wekan.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L`)
- **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:** 15 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-g6vm-7757-pr88

## What is CVE-2026-52890?

CVE-2026-52890 is a high-severity path traversal vulnerability in wekan, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-52890 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52890 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-52890 is a high-severity path traversal vulnerability in wekan, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52890 exists.

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-52890/ (Markdown: https://insights.sbomify.com/CVE-2026-52890/index.md)
```

## Sources

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

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