dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-44735

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 8 weeks old

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 · unedited
OpenProject is open-source, web-based project management software. Prior to 17.3.2 and 17.4.0, the GET /api/v3/shares endpoint returns share details for ALL work packages in a project to any user with the view_shared_work_packages permission. The authorization check operates at the project level only — it does not verify the requesting user can actually view each individual shared work package. This allows a regular project member to discover work package IDs and subjects (including confidential titles), which users have been granted shared access, what role level was assigned (Editor, Commenter, Viewer). This vulnerability is fixed in 17.3.2 and 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 confidence

OpenProject's GET /api/v3/shares endpoint performs authorization only at the project level, returning all shared work package details (including confidential titles, shared users, and role assignments) to any user with view_shared_work_packages permission, regardless of whether they have access to each individual work package. This is an IDOR/authorization bypass vulnerability.

MitigationUpgrade OpenProject to version 17.3.2 or 17.4.0 or later, which implements per-work-package authorization checks.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenProject installation
    Check if OpenProject is running in your environment by looking for the application (typically at /opt/openproject or via docker ps, or check port 80/443 for OpenProject web interface)
    Affected if OpenProject is installed and running
  2. Determine installed version
    Check the OpenProject version via: 1) Web UI: login as admin, go to Administration > Information, or 2) Command line: cat /opt/openproject/config/version.yml or docker exec <container> cat /app/config/version.yml
    Affected if Version is earlier than 17.3.2 or 17.4.0 (vulnerable versions)
  3. Verify API v3 shares endpoint exists
    Make a GET request to /api/v3/shares endpoint using an authenticated session with view_shared_work_packages permission
    Affected if Endpoint responds and returns data (indicates the vulnerable endpoint is present)
  4. Check for view_shared_work_packages permission
    In OpenProject admin panel, navigate to Administration > Roles and Permissions, or query the database: SELECT * FROM roles WHERE permissions LIKE '%view_shared_work_packages%'
    Affected if Any role has the view_shared_work_packages permission granted to non-admin users
  5. Confirm shared work packages exist
    Check if any work packages are shared: GET /api/v3/shares returns non-empty results, or query database: SELECT COUNT(*) FROM member_roles WHERE id IN (SELECT id FROM shares)
    Affected if Shared work packages exist in the system

If OpenProject version is below 17.3.2 or 17.4.0 AND the view_shared_work_packages permission exists AND shared work packages are present, the environment is vulnerable to the authorization bypass.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OpenProject to version 17.3.2 or 17.4.0 or later, which implements per-work-package authorization checks.

Recommended fix High confidence

17.3.2 or 17.4.0

  1. 1. Identify the current OpenProject version by checking the administration panel or running `openproject --version`
  2. 2. Plan upgrade to version 17.3.2 or 17.4.0 (either is a fixed release)
  3. 3. Back up the OpenProject database and configuration files before upgrading
  4. 4. Follow the official OpenProject upgrade guide for your installation method (Docker, package, or source)
  5. 5. Apply the upgrade to the fixed release (17.3.2 or 17.4.0)
  6. 6. Verify the fix by testing the GET /api/v3/shares endpoint with a user who has view_shared_work_packages permission but should not have access to all shared work packages — it should now return only shares for work packages the user can actually view

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44735 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44735 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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