# CVE-2026-44736: OpenProject: Relations API Filter Bypasses Visibility Scope, Leaking Cross-Project Work Package Subjects

> Authenticated users can bypass visibility restrictions to read work package titles from other projects via the Relations 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:** 27 Jun 2026
- **Also known as:** GHSA-p9gq-hrgh-2645

## What is CVE-2026-44736?

CVE-2026-44736 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.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.

Weakness: CWE-836 (Use of Password Hash Instead of Password for Authentication), CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-44736 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44736 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44736 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44736 exists.

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-44736/ (Markdown: https://insights.sbomify.com/CVE-2026-44736/index.md)
```

## Sources

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

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