Quick answers
- Is CVE-2026-67527 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67527 being exploited in the wild.
- How severe is CVE-2026-67527?
- High severity, with a CVSS score of 7.6, published 30 July 2026.
- Which products and versions are affected?
- OpenProject GmbH OpenProject < 17.6.0.
- Is there a fix for CVE-2026-67527?
- A patch was published on 2026-06-19: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67527 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-67527?
- Check whether you run OpenProject GmbH OpenProject at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A missing authorization check (CWE-862) exists in the 'PATCH /api/v3/work_packages/{id}' endpoint. While the endpoint accepted '_links.fileLinks', it failed to verify if the authenticated user possessed the 'manage_file_links' permission. An attacker with 'edit_work_packages' permissions could resolve 'Storages::FileLink' records by their raw ID to detach or hard-delete them. Furthermore, attackers could re-parent FileLinks from other projects to a work package they control, thereby exposing metadata such as origin filenames, IDs, and MIME types. This issue was addressed in version 17.6.0 by moving file link manipulation to the storages module and enforcing consistent validation patterns.
Affected products
- opf OpenProject < 17.6.0
Timeline
- 2026-06-19: patched: Fix committed to repository
- 2026-07-08: advisory: Version 17.6.0 released
- 2026-07-30: disclosed: CVE published