# CVE-2026-67529: Missing authorization in openproject

> Users with time or cost entry permissions can read private work package subjects and IDs via API endpoints due to missing visibility checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 30 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-v3j7-vqwv-5w5q

## What is CVE-2026-67529?

CVE-2026-67529 is a medium-severity missing authorization vulnerability in opf openproject, published on 30 Jul 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.6.0, GET /api/v3/time_entries and GET /api/v3/cost_entries rendered _links.workPackage.title and _links.workPackage.href through associated_resource in modules/costs/lib/api/v3/time_entries/time_entry_representer.rb and modules/costs/lib/api/v3/cost_entries/cost_entry_representer.rb without checking WorkPackage.visible or view_work_packages, allowing users with view_time_entries or view_cost_entries to read private work package subjects and ids. This issue is fixed in 17.6.0.

Weakness: CWE-862 (Missing Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-67529 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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