# CVE-2026-55095: OpenProject: Inplace-edit dialog exposes comments from hidden admin-only project custom fields

> Authenticated non-admin users can view hidden admin-only project custom field comments via the inplace-edit dialog, leading to information disclosure.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA: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:** 20 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-63fg-pgqj-3qf8

## What is CVE-2026-55095?

CVE-2026-55095 is a medium-severity vulnerability in opf openproject, published on 20 Aug 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. In version 17.5.1 and earlier, an authenticated non-admin project member can request the inplace-edit dialog for a raw custom_field_ project attribute. The dialog path resolves the project custom field by its raw identifier without enforcing the normal admin_only visibility scope and renders the stored custom-field comment in read-only mode. This discloses hidden comment text but does not disclose the custom-field value or permit writes or mutation. This issue is reported as fixed in version 17.6.0.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-55095 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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