# CVE-2026-25763: Command Injection on OpenProject repositories leads to Remote Code Execution

> Attackers with repository browse permissions can inject git options to write arbitrary files, leading to remote code execution and data disclosure.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 6 Feb 2026
- **Updated:** 9 Feb 2026
- **Also known as:** GHSA-x37c-hcg5-r5m7

## What is CVE-2026-25763?

CVE-2026-25763 is a critical command injection vulnerability in opf openproject, published on 6 Feb 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. Prior to versions 16.6.7 and 17.0.3, an arbitrary file write vulnerability exists in OpenProject’s repository changes endpoint (/projects/:project_id/repository/changes) when rendering the “latest changes” view via git log. By supplying a specially crafted rev value (for example, rev=--output=/tmp/poc.txt), an attacker can inject git log command-line options. When OpenProject executes the SCM command, Git interprets the attacker-controlled rev as an option and writes the output to an attacker-chosen path. As a result, any user with the :browse_repository permission on the project can create or overwrite arbitrary files that the OpenProject process user is permitted to write. The written contents consist of git log output, but by crafting custom commits the attacker can still upload valid shell scripts, ultimately leading to RCE. The RCE lets the attacker create a reverse shell to the target host and view confidential files outside of OpenProject, such as /etc/passwd. This issue has been patched in versions 16.6.7 and 17.0.3.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Openproject Openproject.

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

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

## Is CVE-2026-25763 being exploited?

There is no known exploitation of CVE-2026-25763 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-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)
- [CVE-2026-22600](https://insights.sbomify.com/CVE-2026-22600/): OpenProject is Vulnerable to Arbitrary File Read via ImageMagick SVG Coder (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25763 is a critical command injection vulnerability in opf openproject, published on 6 Feb 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-25763 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-25763/ (Markdown: https://insights.sbomify.com/CVE-2026-25763/index.md)
```

## Sources

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

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