# CVE-2026-52780: OpenProject: Cache store poisoning leads to Remote Code Execution (RCE)

> Attackers can achieve remote code execution in OpenProject by poisoning the cache store, requiring an upgrade to patched versions.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2026
- **Updated:** 27 Jun 2026
- **Also known as:** GHSA-qj96-f42f-6336

## What is CVE-2026-52780?

CVE-2026-52780 is a critical code injection vulnerability in opf openproject, published on 26 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenProject is open-source, web-based project management software. Prior to 17.3.3 and 17.4.1, cache store poisoning leads to Remote Code Execution (RCE). This vulnerability is fixed in 17.3.3 and 17.4.1.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-52780 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-52780 is a critical code injection vulnerability in opf openproject, published on 26 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-52780 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-52780/ (Markdown: https://insights.sbomify.com/CVE-2026-52780/index.md)
```

## Sources

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

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