dbcve.org
OpenprojectApplication

CVE-2026-24772

CRITICAL · 9.0 CVSS v3.1 Published 2026-01-28
Fix available
A fix is available. Upgrade to 17.0.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenProject is an open-source, web-based project management software. To enable the real time collaboration on documents, OpenProject 17.0 introduced a synchronization server. The OpenPrioject backend generates an authentication token that is currently valid for 24 hours, encrypts it with a shared secret only known to the synchronization server. The frontend hands this encrypted token and the backend URL over to the synchronization server to check user's ability to work on the document and perform intermittent saves while editing. The synchronization server does not properly validate the backend URL and sends a request with the decrypted authentication token to the endpoint that was given to the server. An attacker could use this vulnerability to decrypt a token that he intercepted by other means to gain an access token to interact with OpenProject on the victim's behalf. This vulnerability was introduced with OpenProject 17.0.0 and was fixed in 17.0.2. As a workaround, disable the collaboration feature via Settings -> Documents -> Real time collaboration -> Disable. Additionally the `hocuspocus` container should also be disabled.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenProject 17.0's synchronization server for real-time document collaboration contains a URL validation flaw. The backend generates 24-hour encrypted authentication tokens using a shared secret with the sync server. The sync server decrypts tokens and forwards them to a backend URL provided by the frontend without validating that URL. Attackers who intercept encrypted tokens can trick the sync server into decrypting and relaying the token to an attacker-controlled endpoint, hijacking the victim's session.

MitigationUpgrade to OpenProject 17.0.2 or later. As a workaround, disable the Real time collaboration feature in Settings -> Documents and disable the hocuspocus container.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenprojectApplication
Affected:>= 17.0.0, < 17.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check OpenProject version
    Locate the installed OpenProject version number in the application's about page, package manager, or deployment metadata. This is typically visible in the administration area under 'About' or can be retrieved via the API endpoint /api/v3/about.
    Affected if The installed version is 17.0.0 or 17.0.1 (any version >= 17.0.0 but < 17.0.2).
  2. Verify Real time collaboration status
    Navigate to Settings -> Documents in the OpenProject administration interface and locate the Real time collaboration setting. Check whether it is currently enabled or disabled.
    Affected if The Real time collaboration feature is enabled and the version is in the vulnerable range.
  3. Confirm hocuspocus service is active
    Inspect running processes or containers on the server to determine if the hocuspocus service (collaboration synchronization server) is currently active and listening for connections.
    Affected if The hocuspocus container or service is running and the version is in the vulnerable range.

You are affected if your OpenProject version is 17.0.0 or 17.0.1 AND the Real time collaboration feature is enabled with hocuspocus actively running.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 17.0.2 or later
Fixed in 17.0.2
Interim mitigation

Upgrade to OpenProject 17.0.2 or later. As a workaround, disable the Real time collaboration feature in Settings -> Documents and disable the hocuspocus container.

Recommended fix High confidence

OpenProject 17.0.2

  1. 1. Upgrade OpenProject to version 17.0.2 or later to obtain the security fix
  2. 2. Verify the upgrade was successful by checking the OpenProject version in the admin interface
  3. 3. As an additional precaution, confirm the collaboration feature is properly functioning post-upgrade
  4. 4. If for any reason immediate upgrade is not possible, apply the workaround: navigate to Settings -> Documents -> Real time collaboration and disable it, and also disable the `hocuspocus` container
Caveat Standard upgrade considerations apply - backup database before upgrading, review release notes for any migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openproject Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24772 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data