# CVE-2026-22600: OpenProject is Vulnerable to Arbitrary File Read via ImageMagick SVG Coder

> An attacker with upload permissions can read arbitrary local files by uploading a crafted SVG disguised as a PNG, triggering ImageMagick during PDF export.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/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:** 10 Jan 2026
- **Updated:** 13 Jan 2026
- **Also known as:** GHSA-m8f2-cwpq-vvhh

## What is CVE-2026-22600?

CVE-2026-22600 is a critical path traversal vulnerability in opf openproject, published on 10 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenProject is an open-source, web-based project management software. A Local File Read (LFR) vulnerability exists in the work package PDF export functionality of OpenProject prior to version 16.6.4. By uploading a specially crafted SVG file (disguised as a PNG) as a work package attachment, an attacker can exploit the backend image processing engine (ImageMagick). When the work package is exported to PDF, the backend attempts to resize the image, triggering the ImageMagick text: coder. This allows an attacker to read arbitrary local files that the application user has permissions to access (e.g., /etc/passwd, all project configuration files, private project data, etc.). The attack requires permissions to upload attachments to a container that can be exported to PDF, such as a work package. The issue has been patched in version 16.6.4. Those who are unable to upgrade may apply the patch manually.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Openproject Openproject.

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

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

## Is CVE-2026-22600 being exploited?

There is no known exploitation of CVE-2026-22600 in the wild and no public exploit code.

## Other vulnerabilities in opf openproject

- [CVE-2026-34717](https://insights.sbomify.com/CVE-2026-34717/): OpenProject: SQL Injection in Cost Reporting =n Operator via parse_number_string (critical 9.9)
- [CVE-2026-25763](https://insights.sbomify.com/CVE-2026-25763/): Command Injection on OpenProject repositories leads to Remote Code Execution (critical 9.4)
- [CVE-2026-24685](https://insights.sbomify.com/CVE-2026-24685/): OpenProject has Argument Injection on Repository module that allows Arbitrary File Write (critical 9.4)
- [CVE-2026-32698](https://insights.sbomify.com/CVE-2026-32698/): OpenProject has a SQL Injection via Custom Field Name that can be chained to Remote Code Execution (critical 9.1)
- [CVE-2026-32703](https://insights.sbomify.com/CVE-2026-32703/): OpenProject's repository files are served with the MIME type allowing them to be used to bypass Content Security Policy (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22600 is a critical path traversal vulnerability in opf openproject, published on 10 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22600 in the wild and no public exploit code.

Affected product: opf openproject. 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-22600/ (Markdown: https://insights.sbomify.com/CVE-2026-22600/index.md)
```

## Sources

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

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