Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:Y/R:U/V:C/RE:L/U:GreenSummary
CVE-2025-27017 is a medium-severity Insertion of Sensitive Information into Externally-Accessible File or Directory (CWE-538) vulnerability in Apache Nifi. Its CVSS base score is 6.9 (Medium).
Operationally, ranked in the top 36% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AU-3 (Content of Audit Records) and SI-15 (Information Output Filtering) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-7727
Vulnerability Data
Apache NiFi 1.13.0 through 2.2.0 includes the username and password used to authenticate with MongoDB in the NiFi provenance events that MongoDB components generate during processing. An authorized user with read access to the provenance events of those processors may…
more
see the credentials information. Upgrading to Apache NiFi 2.3.0 is the recommended mitigation, which removes the credentials from provenance event records.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly limits sensitive credential data from being written into provenance event records that function as system-generated audit content.
Filters credential values from processor outputs before they are persisted in provenance events.
Restricts which users can be granted read access to provenance, reducing the population that could observe any inadvertently included credentials.
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.