CVE-2026-67529: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in opf openproject
OpenProject versions prior to 17.6.0 have a vulnerability where certain API endpoints expose private work package titles and IDs to users who have permission to view time or cost entries but not the work packages themselves. This occurs because the API renders work package links without verifying if the user has visibility permissions. The issue is fixed in version 17.6.0.
AI Analysis
Technical Summary
In OpenProject before version 17.6.0, the GET /api/v3/time_entries and GET /api/v3/cost_entries endpoints include _links.workPackage.title and _links.workPackage.href fields via associated_resource in specific representer files. These fields are rendered without checking the WorkPackage.visible attribute or the user's view_work_packages permission. As a result, users with view_time_entries or view_cost_entries permissions can access private work package subjects and IDs, leading to exposure of sensitive information. This vulnerability is classified under CWE-200 (Exposure of Sensitive Information) and CWE-862 (Missing Authorization). The issue is resolved in OpenProject 17.6.0.
Potential Impact
Users with limited permissions (view_time_entries or view_cost_entries) can access private work package titles and IDs, which they should not be authorized to see. This exposure of sensitive information could lead to unauthorized disclosure of project details. There is no indication of impact on data integrity or availability.
Mitigation Recommendations
Upgrade OpenProject to version 17.6.0 or later, where this vulnerability is fixed. There is no official patch or temporary fix other than upgrading. Users should verify that their OpenProject instances are updated to prevent unauthorized exposure of private work package information.
CVE-2026-67529: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in opf openproject
Description
OpenProject versions prior to 17.6.0 have a vulnerability where certain API endpoints expose private work package titles and IDs to users who have permission to view time or cost entries but not the work packages themselves. This occurs because the API renders work package links without verifying if the user has visibility permissions. The issue is fixed in version 17.6.0.
CVSS v3.1
Score 4.3medium
Affected software
opf
openproject
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In OpenProject before version 17.6.0, the GET /api/v3/time_entries and GET /api/v3/cost_entries endpoints include _links.workPackage.title and _links.workPackage.href fields via associated_resource in specific representer files. These fields are rendered without checking the WorkPackage.visible attribute or the user's view_work_packages permission. As a result, users with view_time_entries or view_cost_entries permissions can access private work package subjects and IDs, leading to exposure of sensitive information. This vulnerability is classified under CWE-200 (Exposure of Sensitive Information) and CWE-862 (Missing Authorization). The issue is resolved in OpenProject 17.6.0.
Potential Impact
Users with limited permissions (view_time_entries or view_cost_entries) can access private work package titles and IDs, which they should not be authorized to see. This exposure of sensitive information could lead to unauthorized disclosure of project details. There is no indication of impact on data integrity or availability.
Mitigation Recommendations
Upgrade OpenProject to version 17.6.0 or later, where this vulnerability is fixed. There is no official patch or temporary fix other than upgrading. Users should verify that their OpenProject instances are updated to prevent unauthorized exposure of private work package information.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-29T18:47:17.073Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a6baf0d9c2644c7f89b9bb9
Added to database: 07/30/2026, 20:07:41 UTC
Last enriched: 08/07/2026, 14:58:39 UTC
Last updated: 09/13/2026, 22:01:36 UTC
Views: 54
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.