# CVE-2026-47193: OpenProject information disclosure in journal diff endpoint

Source: https://junglewise.ai/threats/cve-2026-47193-openproject-information-disclosure-in-journal-diff-endpoint  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-26. Updated: 2026-06-26  
License: CC BY 4.0 with a link back

CVE-2026-47193 · Severity: high · CVSS 7.5 · Published 2026-06-26

OpenProject is a web-based project management platform used for tracking tasks, projects, and team collaboration. A security flaw in the software's history tracking system allows unauthorized users to view sensitive information that should be hidden, such as private work package descriptions, internal comments, and restricted project details. This could lead to the exposure of confidential business data or historical records that were intended to be deleted or restricted.

## Quick answers

**Is CVE-2026-47193 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-47193 being exploited in the wild.

**How severe is CVE-2026-47193?** High severity, with a CVSS score of 7.5, published 26 June 2026.

**Which products and versions are affected?** opf OpenProject < 17.3.3, >= 17.4.0 < 17.4.1.

**Is there a fix for CVE-2026-47193?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-47193 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-47193?** Check whether anything you run is named in the advisory. 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

An information disclosure vulnerability exists in OpenProject's journal diff endpoint (GET /journals/:journal_id/diff/:field). The root cause is a failure in the JournalsController to enforce object-level, journal-level, and field-level visibility checks. While the endpoint verifies broad permissions (e.g., view_work_packages), it bypasses specific restrictions such as 'view_internal_comments' or 'view_project_attributes'. An attacker, potentially unauthenticated in public-project configurations, can exploit this to retrieve historical text values for work package descriptions, internal journals, and admin-only custom fields. The vulnerability is fixed in versions 17.3.3 and 17.4.1.

## Affected products

- opf OpenProject < 17.3.3, >= 17.4.0 < 17.4.1

## Timeline

- 2026-06-08: advisory: Original GitHub security advisory published
- 2026-06-26: disclosed: NVD publication date

## References

- [https://github.com/opf/openproject/security/advisories/GHSA-f2rx-x2qj-2hgj](https://github.com/opf/openproject/security/advisories/GHSA-f2rx-x2qj-2hgj)