Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:NSummary
CVE-2025-27150 is a medium-severity Insertion of Sensitive Information into Externally-Accessible File or Directory (CWE-538) vulnerability in Enalean Tuleap. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Credentials In Files (T1552.001); ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-16 (Security and Privacy Attributes) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-7730
Vulnerability Data
Tuleap is an Open Source Suite to improve management of software developments and collaboration. The password to connect the Redis instance is not purged from the archive generated with tuleap collect-system-data. These archives are likely to be used by support…
more
teams that should not have access to this password. The vulnerability is fixed in Tuleap Community Edition 16.4.99.1740492866 and Tuleap Enterprise Edition 16.4-6 and 16.3-11.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
V14.1.2V14.2.8
Mitigating Controls (NIST 800-53 r5) AI
Enforces per-object authorizations so that even if a file or directory is reachable, the sensitive contents remain inaccessible to unauthorized actors.
Associates sensitivity labels with data objects so that subsequent storage or flow decisions can enforce that only appropriately protected files or directories receive the data.
Controls information flows between objects, directly stopping sensitive data from being written into locations whose ACLs or visibility would expose it.
Requires confidentiality protection of information at rest, which can be implemented by restricting storage locations or encrypting contents that would otherwise be placed in externally visible files.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Least-privilege file and directory permissions directly prevent unauthorized actors from reading sensitive data placed in accessible locations.
Protecting data-at-rest encompasses file-level access controls and encryption that stop exposure of sensitive information in externally reachable paths.
Hardened configuration baselines and ongoing config management reduce the chance that sensitive data is written to world-readable files or directories.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
By ensuring that only the minimum necessary data is present in files or directories that may be reachable by external parties, the control lowers the impact of any subsequent exposure.
Requiring visible or metadata labels on classified information helps ensure that files placed in externally accessible locations still carry an explicit sensitivity marker, lowering the likelihood of unnoticed exposure.
The control’s requirement to remove or securely destroy information stored in externally accessible locations reduces the risk of sensitive data being left in files or directories that external parties can reach.
Logging disposals, selecting vetted external disposal services, and protecting media according to classification reduce the likelihood that sensitive information ends up in externally accessible files or directories.
Verifying and sanitizing equipment prior to disposal or resale prevents sensitive files or directories from remaining accessible to external parties who later obtain the hardware.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248579 OL 8 must restrict access to the kernel message buffer. prevents CWE-538
RHEL 8 (1 rule)
- V-230269 RHEL 8 must restrict access to the kernel message buffer. prevents CWE-538