VulnerabilityPublished 29 Jul 2025

CVE-2025-52899: Enalean tuleap · Observable Response Discrepancy

Affects Enalean tuleapSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 16.9-2 when convenient.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 16.9-2

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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 29 Jul 2025
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 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 enalean/tuleap to 16.9-2.

Affected software

Product	Affected	Fixed in
GitHubenalean/tuleap`pkg:github/enalean/tuleap`Other threats	Affected <16.9-2	Fixed in 16.9-2

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

AI-suggested

To mitigate CVE-2025-52899, European organizations should take the following specific actions: 1) Upgrade all Tuleap installations to the patched versions: Community Edition 16.9.99.1750843170 or later, and Enterprise Edition 16.8-4 or 16.9-2 or later. 2) If immediate upgrading is not feasible, implement temporary mitigations such as customizing the forgot password response messages to be uniform regardless of user existence, thereby eliminating observable response discrepancies. 3) Monitor application logs for unusual or repeated forgot password requests that could indicate enumeration attempts. 4) Employ web application firewalls (WAFs) with rules designed to detect and block automated enumeration patterns targeting the forgot password endpoint. 5) Educate users and administrators about phishing risks that may arise from leaked user information and enforce strong authentication mechanisms like multi-factor authentication (MFA) to reduce the impact of compromised credentials. 6) Regularly audit and review user account management policies to ensure inactive or unnecessary accounts are disabled or removed, minimizing the attack surface. These targeted measures go beyond generic advice by addressing the specific enumeration vector and reinforcing overall account security posture.

Description

Tuleap is an Open Source Suite created to facilitate management of software development and collaboration. In Tuleap Community Edition prior to version 16.9.99.1750843170 and Tuleap Enterprise Edition prior to 16.8-4 and 16.9-2, the forgot password form allows for user enumeration. This is fixed in Tuleap Community Edition version 16.9.99.1750843170 and Tuleap Enterprise Edition 16.8-4 and 16.9-2.

Impact

For European organizations using Tuleap for software development and collaboration, this vulnerability poses a moderate risk primarily related to confidentiality. User enumeration can enable attackers to harvest valid usernames or email addresses, which can be leveraged in subsequent attacks like credential stuffing, phishing campaigns, or social engineering. While the vulnerability does not directly compromise system integrity or availability, the exposure of user information can undermine trust and potentially lead to unauthorized access if combined with other attack vectors. Organizations in sectors with stringent data protection regulations, such as GDPR, may face compliance risks if user data is exposed or exploited. Additionally, software development teams relying on Tuleap for project management could experience indirect impacts if attackers use enumerated user data to impersonate employees or disrupt workflows. The lack of known exploits reduces immediate risk, but the ease of exploitation (no authentication or user interaction required) means that attackers could automate reconnaissance efforts against vulnerable installations. Therefore, European organizations should consider this vulnerability a significant information disclosure risk that warrants timely remediation to protect user privacy and maintain operational security.

CWE-204Observable Response Discrepancy (opens in a new tab)
Base weakness
The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.
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.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (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
ICMP IP Total Length Field Probe (opens in a new tab)
ICMP IP 'ID' Field Error Message Probe (opens in a new tab)
Application Fingerprinting (opens in a new tab)
System Footprinting (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 29 Jul 2025, 19:47 UTC

WeaknessesCWE-204

Technical details

References

Community reviews

Related threats