VulnerabilityPublished 28 Jan 2026

CVE-2026-24772: opf openproject · Insufficient Verification of Data Authenticity

Affects opf openprojectSource CVE Database V5

Not known to be exploited · CVSS 8.9 High : upgrade to 17.0.2 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

8.9High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 17.0.2

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: High
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade opf/openproject to 17.0.2.

Affected software

Product	Affected	Fixed in
opfopenproject	Affected =OpenProject >= 17.0.0, < 17.0.2 =openproject/hocuspocus < 17.0.2	Fixed in–
GitHubopf/openproject`pkg:github/opf/openproject`Other threats	Affected <17.0.2	Fixed in 17.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediately upgrade OpenProject installations to version 17.0.2 or later, which contains the fix for this vulnerability.
If immediate patching is not possible, disable the real-time collaboration feature via Settings -> Documents -> Real time collaboration -> Disable.
Disable the hocuspocus container responsible for synchronization to prevent token leakage.
Restrict network access to the synchronization server and backend URLs to trusted hosts only, using firewall rules or network segmentation.
Monitor network traffic for unusual requests to backend URLs or unexpected external endpoints that could indicate exploitation attempts.
Implement TLS encryption for all communications to reduce risk of token interception.
Educate users about the risk of using OpenProject on untrusted networks and encourage use of VPNs.
Review and rotate shared secrets used for token encryption if compromise is suspected.
Conduct regular audits of OpenProject logs to detect anomalous access patterns or token misuse.
Coordinate with OpenProject support or community for updates and security advisories.

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.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of project management data stored and managed within OpenProject. Unauthorized access via token theft can lead to data leakage, unauthorized document modifications, and potential disruption of project workflows. Organizations relying on OpenProject for sensitive or regulated projects (e.g., government, finance, healthcare, or critical infrastructure sectors) could face compliance violations and reputational damage if exploited. The ability for an attacker to impersonate legitimate users may also facilitate lateral movement within networks or further attacks on integrated systems. Since OpenProject is used widely across Europe in both public and private sectors, the impact could be broad, especially in environments where real-time collaboration is enabled and network interception is feasible (e.g., unsecured Wi-Fi, compromised internal networks). The limited availability impact reduces risk of denial-of-service but does not diminish the criticality of confidentiality and integrity breaches.

CWE-345Insufficient Verification of Data Authenticity (opens in a new tab)
Class weaknessOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
XML Security (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
REST Assessment (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.2 (opens in a new tab)
V3.5.3 (opens in a new tab)
V13.2.6 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cache Poisoning (opens in a new tab)
DNS Cache Poisoning (opens in a new tab)
Spoofing of UDDI/ebXML Messages (opens in a new tab)
Application API Message Manipulation via Man-in-the-Middle (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/opf/openproject/security/advisories/GHSA-r854-p5qj-x974 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Jan 2026, 18:35 UTC

WeaknessesCWE-345

Technical details

References

Community reviews

Related threats