# CVE-2026-44735: OpenProject: Shares API Information Disclosure

> A regular project member can view confidential work package details and share permissions due to insufficient authorization checks in the Shares API.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 26 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-cfg3-f34w-9xx5

## What is CVE-2026-44735?

CVE-2026-44735 is a medium-severity missing authorization vulnerability in opf openproject, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-44735 being exploited?

There is no known exploitation of CVE-2026-44735 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44735 is a medium-severity missing authorization vulnerability in opf openproject, published on 26 Jun 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-44735 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-44735/ (Markdown: https://insights.sbomify.com/CVE-2026-44735/index.md)
```

## Sources

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

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