# CVE-2026-47193: OpenProject: Journal diff endpoint bypasses object, journal, and field visibility checks

> Attackers can access hidden historical field values via the journal diff endpoint due to missing visibility checks in OpenProject.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-f2rx-x2qj-2hgj

## What is CVE-2026-47193?

CVE-2026-47193 is a high-severity missing authorization vulnerability in opf openproject, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenProject is open-source, web-based project management software. Prior to 17.3.3 and 17.4.1, the journal diff endpoint discloses hidden historical field values without enforcing object and field visibility. This vulnerability is fixed in 17.3.3 and 17.4.1.

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

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


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

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

## Is CVE-2026-47193 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47193 is a high-severity missing authorization vulnerability in opf openproject, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47193 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-47193/ (Markdown: https://insights.sbomify.com/CVE-2026-47193/index.md)
```

## Sources

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

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