# CVE-2026-24772: OpenProject has SSRF and CSWSH in Hocuspocus Synchronization Server > Attackers can exploit SSRF in the synchronization server to decrypt intercepted tokens and gain unauthorized access to OpenProject accounts. - **Severity:** High 8.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 28 Jan 2026 - **Updated:** 28 Jan 2026 - **Also known as:** GHSA-r854-p5qj-x974 ## What is CVE-2026-24772? CVE-2026-24772 is a high-severity server-side request forgery vulnerability in opf openproject, published on 28 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-345 (Insufficient Verification of Data Authenticity) ## Which versions are affected by CVE-2026-24772? It affects 1 product. Products: Openproject Openproject. ## How do I fix CVE-2026-24772? No fix has been published for CVE-2026-24772 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-24772 being exploited? There is no known exploitation of CVE-2026-24772 in the wild and no public exploit code. ## Other vulnerabilities in opf openproject - [CVE-2026-34717](https://insights.sbomify.com/CVE-2026-34717/): OpenProject: SQL Injection in Cost Reporting =n Operator via parse_number_string (critical 9.9) - [CVE-2026-25763](https://insights.sbomify.com/CVE-2026-25763/): Command Injection on OpenProject repositories leads to Remote Code Execution (critical 9.4) - [CVE-2026-24685](https://insights.sbomify.com/CVE-2026-24685/): OpenProject has Argument Injection on Repository module that allows Arbitrary File Write (critical 9.4) - [CVE-2026-32698](https://insights.sbomify.com/CVE-2026-32698/): OpenProject has a SQL Injection via Custom Field Name that can be chained to Remote Code Execution (critical 9.1) - [CVE-2026-32703](https://insights.sbomify.com/CVE-2026-32703/): OpenProject's repository files are served with the MIME type allowing them to be used to bypass Content Security Policy (critical 9.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-24772 and fix it if it is affected. What it is: CVE-2026-24772 is a high-severity server-side request forgery vulnerability in opf openproject, published on 28 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-24772 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-24772/ (Markdown: https://insights.sbomify.com/CVE-2026-24772/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24772 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24772 - OSV: https://osv.dev/vulnerability/CVE-2026-24772 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-24772/ Summaries are generated and may contain mistakes; the official description above is the record.