Apache Software Foundation Apache Nifi vulnerabilities

CVE-2026-82561 [MEDIUM] CWE-862 CVE-2026-82561: Apache NiFi 1.5.0 through 2.11.0 provide REST API methods that replace the entire contents of a Proc Apache NiFi 1.5.0 through 2.11.0 provide REST API methods that replace the entire contents of a Process Group using a client-supplied flow definition, covering Process Group flow replacement together with versioned flow update and rebase operations. Framework authorization for these methods was limited to read and write privileges on the Process Gro

CVE-2017-5635 [HIGH] CWE-287 CVE-2017-5635: In Apache NiFi before 0.7.2 and 1.x before 1.1.2 in a cluster environment, if an anonymous user requ In Apache NiFi before 0.7.2 and 1.x before 1.1.2 in a cluster environment, if an anonymous user request is replicated to another node, the originating node identity is used rather than the "anonymous" user.

CVE-2017-12632 [HIGH] CWE-20 CVE-2017-12632: A malicious host header in an incoming HTTP request could cause NiFi to load resources from an exter A malicious host header in an incoming HTTP request could cause NiFi to load resources from an external server. The fix to sanitize host headers and compare to a controlled whitelist was applied on the Apache NiFi 1.5.0 release. Users running a prior 1.x release should upgrade to the appropriate release.

CVE-2024-37389 [MEDIUM] CWE-79 CVE-2024-37389: Apache NiFi 1.10.0 through 1.26.0 and 2.0.0-M1 through 2.0.0-M3 support a description field in the P Apache NiFi 1.10.0 through 1.26.0 and 2.0.0-M1 through 2.0.0-M3 support a description field in the Parameter Context configuration that is vulnerable to cross-site scripting. An authenticated user, authorized to configure a Parameter Context, can enter arbitrary JavaScript code, which the client browser will execute within the session context of the

CVE-2023-40037 [MEDIUM] CWE-184 CVE-2023-40037: Apache NiFi 1.21.0 through 1.23.0 support JDBC and JNDI JMS access in several Processors and Control Apache NiFi 1.21.0 through 1.23.0 support JDBC and JNDI JMS access in several Processors and Controller Services with connection URL validation that does not provide sufficient protection against crafted inputs. An authenticated and authorized user can bypass connection URL validation using custom input formatting. The resolution enhances connection

CVE-2018-17194 [HIGH] CWE-20 CVE-2018-17194: When a client request to a cluster node was replicated to other nodes in the cluster for verificatio When a client request to a cluster node was replicated to other nodes in the cluster for verification, the Content-Length was forwarded. On a DELETE request, the body was ignored, but if the initial request had a Content-Length value other than 0, the receiving nodes would wait for the body and eventually timeout. Mitigation: The fix to check DELETE re

CVE-2026-25903 [MEDIUM] CWE-862 CVE-2026-25903: Apache NiFi 1.1.0 through 2.7.2 are missing authorization when updating configuration properties on Apache NiFi 1.1.0 through 2.7.2 are missing authorization when updating configuration properties on extension components that have specific Required Permissions based on the Restricted annotation. The Restricted annotation indicates additional privileges required to add the annotated component to the flow configuration, but framework authorization di

CVE-2023-34212 [MEDIUM] CWE-502 CVE-2023-34212: The JndiJmsConnectionFactoryProvider Controller Service, along with the ConsumeJMS and PublishJMS Pr The JndiJmsConnectionFactoryProvider Controller Service, along with the ConsumeJMS and PublishJMS Processors, in Apache NiFi 1.8.0 through 1.21.0 allow an authenticated and authorized user to configure URL and library properties that enable deserialization of untrusted data from a remote location. The resolution validates the JNDI URL and restricts

CVE-2025-27017 [MEDIUM] CWE-538 CVE-2025-27017: Apache NiFi 1.13.0 through 2.2.0 includes the username and password used to authenticate with MongoD 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 see the credentials information. Upgrading to Apache NiFi 2.3.0 is the recommended

CVE-2018-17195 [HIGH] CWE-319 CVE-2018-17195: The template upload API endpoint accepted requests from different domain when sent in conjunction wi The template upload API endpoint accepted requests from different domain when sent in conjunction with ARP spoofing + man in the middle (MiTM) attack, resulting in a CSRF attack. The required attack vector is complex, requiring a scenario with client certificate authentication, same subnet access, and injecting malicious code into an unprotected (plai

CVE-2017-12623 [MEDIUM] CWE-611 CVE-2017-12623: An authorized user could upload a template which contained malicious code and accessed sensitive fil An authorized user could upload a template which contained malicious code and accessed sensitive files via an XML External Entity (XXE) attack. The fix to properly handle XML External Entities was applied on the Apache NiFi 1.4.0 release. Users running a prior 1.x release should upgrade to the appropriate release.

CVE-2021-44145 [MEDIUM] CWE-200 CVE-2021-44145: In the TransformXML processor of Apache NiFi before 1.15.1 an authenticated user could configure an In the TransformXML processor of Apache NiFi before 1.15.1 an authenticated user could configure an XSLT file which, if it included malicious external entity calls, may reveal sensitive information.

CVE-2017-7667 [HIGH] CWE-346 CVE-2017-7667: Apache NiFi before 0.7.4 and 1.x before 1.3.0 need to establish the response header telling browsers Apache NiFi before 0.7.4 and 1.x before 1.3.0 need to establish the response header telling browsers to only allow framing with the same origin.

CVE-2018-17192 [MEDIUM] CWE-1021 CVE-2018-17192: The X-Frame-Options headers were applied inconsistently on some HTTP responses, resulting in duplica The X-Frame-Options headers were applied inconsistently on some HTTP responses, resulting in duplicate or missing security headers. Some browsers would interpret these results incorrectly, allowing clickjacking attacks. Mitigation: The fix to consistently apply the security headers was applied on the Apache NiFi 1.8.0 release. Users running a prior

CVE-2026-54665 [MEDIUM] CWE-346 CVE-2026-54665: Apache NiFi 0.0.1 through 2.9.0 support building qualified URLs from one of several HTTP request hea Apache NiFi 0.0.1 through 2.9.0 support building qualified URLs from one of several HTTP request headers that provide an alternative to the standard Host header without validating the values provided. Apache NiFi 1.6.0 introduced a configurable application property to restrict values provided in the HTTP Host header, but did not apply the validation

CVE-2020-1928 [MEDIUM] CWE-532 CVE-2020-1928: An information disclosure vulnerability was found in Apache NiFi 1.10.0. The sensitive parameter par An information disclosure vulnerability was found in Apache NiFi 1.10.0. The sensitive parameter parser would log parsed values for debugging purposes. This would expose literal values entered in a sensitive property when no parameter was present.

CVE-2017-7665 [MEDIUM] CWE-79 CVE-2017-7665: In Apache NiFi before 0.7.4 and 1.x before 1.3.0, there are certain user input components in the UI In Apache NiFi before 0.7.4 and 1.x before 1.3.0, there are certain user input components in the UI which had been guarding for some forms of XSS issues but were insufficient.

CVE-2020-1933 [MEDIUM] CWE-79 CVE-2020-1933: A XSS vulnerability was found in Apache NiFi 1.0.0 to 1.10.0. Malicious scripts could be injected to A XSS vulnerability was found in Apache NiFi 1.0.0 to 1.10.0. Malicious scripts could be injected to the UI through action by an unaware authenticated user in Firefox. Did not appear to occur in other browsers.

CVE-2026-81866 [MEDIUM] CWE-862 CVE-2026-81866: Apache NiFi 2.9.0 through 2.11.0 provide Connector configuration update and verification REST API me Apache NiFi 2.9.0 through 2.11.0 provide Connector configuration update and verification REST API methods that do not enforce authorization checking on Assets and Secrets referenced in proposed configuration. Updating or verifying a Connector configuration step can apply Asset and Secret references, but framework authorization was limited to write p

CVE-2026-62354 [MEDIUM] CWE-863 CVE-2026-62354: Authorization handling for Parameter Context validation requests in Apache NiFi 1.10.0 through 2.10. Authorization handling for Parameter Context validation requests in Apache NiFi 1.10.0 through 2.10.0 allows clients with read access to submit proposed Parameter values. The proposed values override current configuration, enabling users with read access to invoke predefined component validation methods with alternative settings. Apache NiFi install