VulnerabilityPublished 10 Jan 2026Updated 13 Jan 2026

CVE-2026-22602: opf openproject · Information Exposure

Affects opf openprojectSource CVE Database V5

Not known to be exploited · CVSS 3.5 Low : upgrade to 16.6.2 when convenient.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

3.5Low

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

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: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 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 openproject and opf/openproject to 16.6.2.

Affected software

Product	Affected	Fixed in
opfopenproject	Affected <16.6.2	Fixed in 16.6.2
GitHubopf/openproject`pkg:github/opf/openproject`Other threats	Affected <16.6.2	Fixed in 16.6.2

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

AI-suggested

The most effective mitigation is to upgrade OpenProject installations to version 16.6.2 or later, where the vulnerability is fully patched. For organizations unable to upgrade immediately, applying the vendor-provided manual patch is recommended to block unauthorized user enumeration. Additionally, restricting access to the OpenProject API and user enumeration endpoints to trusted IP ranges or VPNs can reduce exposure. Implementing strict role-based access controls to limit low-privileged user capabilities and monitoring API usage logs for unusual enumeration patterns can help detect exploitation attempts. Organizations should also educate users about phishing risks that could leverage disclosed user names. Finally, reviewing and minimizing the amount of user information exposed in the UI and API responses can reduce the impact of similar vulnerabilities.

Description

OpenProject is an open-source, web-based project management software. Prior to version 16.6.2, a low‑privileged logged-in user can view the full names of other users. Since user IDs are assigned sequentially and predictably (e.g., 1 to 1000), an attacker can extract a complete list of all users’ full names by iterating through these URLs. The same behavior can also be reproduced via the OpenProject API, allowing automated retrieval of full names through the API as well. This issue has been patched in version 16.6.2. Those who are unable to upgrade may apply the patch manually.

Impact

For European organizations, the primary impact of CVE-2026-22602 is the unauthorized disclosure of user full names within OpenProject instances running vulnerable versions. While full names alone may seem low risk, they can facilitate targeted social engineering, spear-phishing campaigns, or privacy violations under GDPR regulations. Organizations handling sensitive projects or personal data could face reputational damage or regulatory scrutiny if user information is exposed. The vulnerability does not allow access to more sensitive credentials or system control, so direct operational disruption or data integrity compromise is unlikely. However, the ease of automated enumeration via the API increases the risk of large-scale data harvesting. European entities using OpenProject for project management, especially in sectors like government, finance, or critical infrastructure, should consider this a privacy risk that requires timely remediation to maintain compliance and reduce attack surface.

Summary

CVE-2026-22602 is a vulnerability classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) affecting OpenProject, an open-source web-based project management software. The flaw exists in versions prior to 16.6.2, where a low-privileged authenticated user can access the full names of other users by exploiting the predictable sequential user ID assignment. By iterating through user IDs in URLs or via the OpenProject API, an attacker can systematically retrieve the full names of all users registered in the system. This information disclosure does not extend to more sensitive data such as passwords or personal identifiers beyond full names, nor does it allow modification or disruption of data or services. The vulnerability requires that the attacker be logged in with at least low-level privileges and involves user interaction to perform the enumeration. The issue was addressed and patched in OpenProject version 16.6.2, with the vendor recommending upgrades or manual patch application for those unable to update immediately. The CVSS v3.1 score of 3.5 reflects a low-severity rating due to limited confidentiality impact, no integrity or availability impact, and relatively straightforward exploitation given authentication and user interaction requirements. No known exploits have been reported in the wild, but the vulnerability could be leveraged for reconnaissance or social engineering purposes.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Jan 2026, 07:43 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats