CVE-2026-24685
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. Versions prior to 16.6.6 and 17.0.2 have an arbitrary file write vulnerability in OpenProject’s repository diff download endpoint (`/projects/:project_id/repository/diff.diff`) when rendering a single revision via git show. By supplying a specially crafted rev value (for example, `rev=--output=/tmp/poc.txt)`, an attacker can inject git show 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 show output (commit metadata and patch), but overwriting application or configuration files still leads to data loss and denial of service, impacting integrity and availability. The issue has been fixed in OpenProject 17.0.2 and 16.6.6.
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.6 and 17.0.2 contain an argument injection vulnerability in the repository diff download endpoint where the `rev` parameter is passed unsanitized to the `git show` command. Attackers with `:browse_repository` permission can inject git options (e.g., `--output=/tmp/poc.txt`) to write arbitrary files to locations the OpenProject process user can access, leading to potential data loss and denial of service.
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.6>= 17.0.0, < 17.0.2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Identify installed OpenProject versionAccess the OpenProject web UI and navigate to Administration > Information, or query the API endpoint /api/v3/configuration, or check the installed package version via package manager or GemfileAffected if Version is less than 16.6.6 or greater than or equal to 17.0.0 but less than 17.0.2
-
Verify repository module is enabledNavigate to Administration > Plugins (or equivalent) to confirm the repositories module is active, or check project settings for individual projects that have a Repositories tabAffected if The repository module is enabled for any project in the system
-
Check for users with browse_repository permissionNavigate to Administration > Users and Roles > Roles, and inspect each role to see if the :browse_repository permission is granted, or check the roles assigned to users with repository accessAffected if Any role assigned to users includes the :browse_repository permission, allowing repository browsing functionality
-
Confirm external repository integration existsNavigate to project settings and check if any project has an external repository (Git, Subversion, etc.) configured under the Repository tabAffected if External repositories are configured and linked to projects in OpenProject
You are affected if your OpenProject version falls below 16.6.6 or is between 17.0.0 and 17.0.2 AND the repository module is enabled with users having :browse_repository permission and at least one project using external repositories.
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.617.0.2
Upgrade to OpenProject 16.6.6 or 17.0.2 or later to patch the vulnerability. If immediate patching is not feasible, disable or restrict the repository browsing functionality until the upgrade can be completed.
16.6.6 (for 16.x users) or 17.0.2 (for 17.x users)
- 1. Determine current OpenProject version by checking the administration panel or running `openproject --version`
- 2. If running version 16.x (below 16.6.6), plan upgrade to version 16.6.6
- 3. If running version 17.0.0 or 17.0.1, plan upgrade to version 17.0.2
- 4. Review OpenProject upgrade documentation for your deployment method (package manager, Docker, or source)
- 5. Create a backup of the OpenProject database and configuration files before upgrading
- 6. Perform the upgrade following the official upgrade path for your installation method
- 7. After upgrade, verify the version number matches the expected fixed release (16.6.6 or 17.0.2)
- 8. Test that the repository diff download functionality works correctly and the vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24685 — 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-24685 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