CVE-2026-44736
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 open-source, web-based project management software. Prior to 17.4.0, the GET /api/v3/relations endpoint allows any authenticated user to retrieve relations — and the subject (title) of work packages they have no permission to view — by supplying an arbitrary work package ID in the involved, fromId, or toId filter. This bypasses the Relation.visible scope due to a flawed performance optimization in RelationQuery. This vulnerability is fixed in 17.4.0.
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 confidenceThe GET /api/v3/relations endpoint in OpenProject versions prior to 17.4.0 allows any authenticated user to access work package subjects (titles) they lack permission to view by supplying arbitrary work package IDs in the involved, fromId, or toId filter parameters. The vulnerability stems from a flawed performance optimization in RelationQuery that bypasses the Relation.visible permission scope.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 OpenProject versionCheck the installed OpenProject version by running 'openproject --version' or inspecting the Gemfile.lock in the installation directory, or checking the administration panel under 'System' settings.Affected if The installed version is prior to 17.4.0 (e.g., 17.3.x, 17.2.x, or older)
-
Confirm API endpoint accessibilityVerify that the OpenProject API is accessible by attempting to authenticate and making a request to GET /api/v3/relations with any valid authenticated user session.Affected if The API endpoint responds to authenticated requests (even low-privilege users can access /api/v3/relations)
-
Test for permission bypass via filter parametersSubmit a GET request to /api/v3/relations?involved=<work_package_id> where <work_package_id> refers to a work package the authenticated user should not have permission to view. Check if the response returns the work package subject/title.Affected if The response includes work package subjects/titles that the user lacks permission to view, exposing the vulnerability
A user is affected if OpenProject version is below 17.4.0 AND the /api/v3/relations endpoint is accessible to authenticated users who can query work package subjects they should not have permission to see.
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 · scopedUpgrade OpenProject to version 17.4.0 or later to apply the fix that properly enforces the Relation.visible permission scope.
17.4.0
- 1. Backup your OpenProject database and installation before upgrading.
- 2. Upgrade OpenProject to version 17.4.0 or later.
- 3. After upgrading, verify that the /api/v3/relations endpoint properly enforces permission checks on the involved, fromId, and toId filters.
- 4. Confirm that users can no longer retrieve relation data or work package subject titles for work packages they do not have permission to view.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44736 — 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-44736 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