LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24772: OpenProject has SSRF and CSWSH in Hocuspocus Synchronization Server

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.

HighCVSS 8.9Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

OpenProject 17.0 added real-time document collaboration using a Hocuspocus synchronization server. A validation flaw can let an authenticated attacker misuse an intercepted encrypted token and backend URL handling to obtain an access token for a victim. Fixed versions are available. Organizations using OpenProject 17.0.0 or 17.0.1 with collaboration enabled should prioritize remediation.

Executive priority

Treat as urgent for affected OpenProject 17.0 deployments with collaboration enabled. The flaw can enable victim-level access if prerequisites are met. Patch to 17.0.2 or disable collaboration and Hocuspocus until patched. No active exploitation is confirmed in the supplied sources.

Technical view

CVE-2026-24772 affects OpenProject >=17.0.0 and <17.0.2, including openproject/hocuspocus <17.0.2. The synchronization server insufficiently validates a backend URL, then sends a decrypted authentication token to the supplied endpoint. The advisory describes SSRF and CSWSH impacts. CVSS is 8.9, with low attack complexity, required privileges, required user interaction, and high confidentiality and integrity impact.

Likely exposure

Exposure is likely limited to OpenProject deployments on 17.0.0 or 17.0.1 using the real-time collaboration feature and Hocuspocus synchronization server. Deployments below 17.0.0 are not described as affected by the source. Version 17.0.2 is listed as fixed.

Exploitation context

The CVE record does not indicate CISA KEV listing, and the provided sources do not report active exploitation. Exploitation requires attacker privileges, user interaction, and token interception by other means, according to the description. Business risk is impersonation of a victim inside OpenProject and potential data access or modification.

Researcher notes

The public description centers on improper backend URL validation and token forwarding by the Hocuspocus synchronization server. CWE is listed as CWE-345. The source bundle does not provide exploit details, indicators of compromise, or evidence of active exploitation. Validate exposure through version, feature state, and container deployment.

Mitigation direction

  • Upgrade OpenProject and openproject/hocuspocus to version 17.0.2 or later.
  • If upgrade is delayed, disable real-time collaboration in OpenProject document settings.
  • Also disable the hocuspocus container when using the workaround.
  • Review the vendor advisory for any deployment-specific guidance.

Validation and detection

  • Inventory OpenProject deployments and identify versions 17.0.0 and 17.0.1.
  • Check whether real-time document collaboration is enabled.
  • Confirm whether the hocuspocus container is running.
  • Verify upgraded systems report OpenProject and hocuspocus version 17.0.2 or later.
  • Review logs for unusual synchronization-server backend URL activity where available.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-345: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24772 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.9CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L2.36Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.9High
CVSS 3.1 vector shape for CVE-2026-24772Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
opfopenprojectOpenProject >= 17.0.0, < 17.0.2, openproject/hocuspocus < 17.0.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-345 · source CWE mapping

Insufficient Verification of Data Authenticity

Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.