CVE-2026-25763
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenProject 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenProject versions prior to 16.6.7 and 17.0.3 contain an arbitrary file write vulnerability in the repository changes endpoint (/projects/:project_id/repository/changes). Attackers with :browse_repository permission can inject git log CLI options via a crafted rev parameter (e.g., rev=--output=/tmp/poc.txt), causing Git to write git log output to attacker-controlled paths. Although content is git log output, attackers can craft commits to upload shell scripts and achieve RCE.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 16.6.7>= 17.0.0, < 17.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed OpenProject versionRun 'openproject --version' or check the OpenProject administration panel under Administration > Information for the exact version numberAffected if version is less than 16.6.7 OR (version greater than or equal to 17.0.0 AND less than 17.0.3)
-
Check if repository module is enabledNavigate to Administration > Projects > Select a project > Modules, or query the database for enabled modules where name contains 'repository'Affected if the repository module is enabled on any project
-
Verify :browse_repository permission existsCheck user roles in Administration > Users & Permissions > Roles, or query the database tables for role permissions where permission = 'browse_repository'Affected if any role includes the :browse_repository permission assigned to non-admin users
-
Confirm repository is configured for any projectNavigate to Project > Settings > Repositories, or query the database for any entry in the repositories tableAffected if at least one project has a Git or other repository configured
If the installed version falls within the affected ranges AND the repository module with browse_repository permission is enabled on any project, the environment is vulnerable to arbitrary file write via the repository changes endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped16.6.717.0.3
Upgrade OpenProject to version 16.6.7 or 17.0.3 or later to patch the arbitrary file write vulnerability. If immediate upgrade is not possible, restrict or temporarily revoke the :browse_repository permission from untrusted users.
Upgrade to OpenProject 16.6.7 (for the 16.x line) or 17.0.3 (for the 17.x line)
- Backup your OpenProject database and configuration files before proceeding with the upgrade
- Stop the OpenProject service (e.g., sudo openproject stop or systemctl stop openproject)
- If using the APT package manager on Debian/Ubuntu, run: sudo apt-get update && sudo apt-get install openproject
- If using the RPM package on RHEL/CentOS, run: sudo yum update openproject
- Alternatively, if using Docker, update the image tag to openproject:16.6.7 or openproject:17.0.3 and recreate the container
- Run database migrations: sudo openproject run rake db:migrate (or through the web interface during first startup)
- Restart the OpenProject service (e.g., sudo openproject start or systemctl start openproject)
- Verify the upgrade by logging in and checking the version in Administration > Information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25763 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25763 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data