Apache NiFi Vulnerabilities Allow Authorization Bypass and Remote Code Execution

Apache NiFi has disclosed four security vulnerabilities affecting its web API, including authorization-bypass flaws, a potential remote code execution pathway, and a resource-exhaustion issue involving gzip-compressed REST requests.

Organizations running affected Apache NiFi releases should upgrade to version 2.11.0, which addresses all reported issues.

The most severe issue, tracked as CVE-2026-68981 and NIFI-16152, affects NiFi versions 1.5.0 through 2.10.0. The vulnerability stems from how the application REST API handles gzip-encoded HTTP requests.

Apache NiFi Vulnerabilities

NiFi previously relied on a Jersey encoding filter that enforced the configured maximum request size against the compressed payload rather than the fully decompressed content.

An attacker could craft a small gzip-compressed request that expands significantly after decompression, forcing the NiFi server to allocate excessive memory.

Successful exploitation could result in resource exhaustion and service disruption, particularly where the REST API is exposed to untrusted or insufficiently restricted clients.

Apache NiFi 2.11.0 mitigates the issue by moving response compression to Jetty Server and disabling decompression of gzip-encoded HTTP requests.

A second high-severity vulnerability, CVE-2026-62354 or NIFI-16112, affects NiFi versions 1.10.0 through 2.10.0. It concerns authorization for Parameter Context validation requests.

Prior to version 2.11.0, users with read-only access to a Parameter Context could submit proposed Parameter values as part of a validation request.

These supplied values could override existing configuration during validation, allowing a read-authorized user to invoke predefined component validation methods using attacker-controlled settings.

The flaw is most relevant in deployments that enforce different permissions for viewing and modifying Parameter Context configurations.

Version 2.11.0 corrects the authorization model by requiring write permissions before clients can submit Parameter Context validation requests. Nguyen Van Hiep of MBBank discovered the issue.

Apache also addressed CVE-2026-68979 (NIFI-16148), a medium-severity authorization issue that can lead to code execution under specific deployment conditions.

NiFi’s Parameter Context update API did not check authorization on components that reference the updated Parameter values. An authenticated user permitted to modify a Parameter Context but not the affected components could change the values used by those components.

In environments that use component-level authorization, this could become especially serious when a Parameter contains executable script content.

Updating the Parameter may trigger code execution during automatic component validation, even if the affected component is not started.

Existing verification checks limit the impact to components that are stopped. NiFi 2.11.0 now performs authorization checks on affected referencing components.

Finally, CVE-2026-68980 (NIFI-16154) affects NiFi 2.0.0 through 2.10.0 and allows unauthorized deletion of Parameter Context Assets. NiFi authorized deletion using a supplied Parameter Context identifier without confirming that it matched the Asset’s stored owner.

This could permit unauthorized Asset deletion where Parameter Contexts are subject to different authorization levels.

Administrators should prioritize upgrading to Apache NiFi 2.11.0, review component-level and Parameter Context authorization policies, and restrict REST API access to trusted networks and authenticated users.

Cut SOC investigation blind spots and contain threats earlier to reduce response costs and business disruption with ANY.RUN. 

Tamilselvan
Tamilselvanhttps://cyberpress.org/
Tamilselvan is an Investigative cybersecurity journalist dedicated to breaking stories on ransomware cartels, data breaches, and state-sponsored espionage.

Trending News

Related Stories