CVE-2026-54665 Affecting apache-nifi package, versions <2.10.0-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.27% (19th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-APACHENIFI-17457854
  • published25 Jun 2026
  • disclosed22 Jun 2026

Introduced: 22 Jun 2026

CVE-2026-54665  (opens in a new tab)

How to fix?

Upgrade Minimos:latest apache-nifi to version 2.10.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream apache-nifi package and not the apache-nifi package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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 to alternative Proxy and Forwarded headers. The absence of proxy host header validation allowed a client to instruct Apache NiFi web services to construct invalid qualified URLs for redirection or data references. Upgrading to Apache NiFi 2.10.0 is the recommended mitigation, which implements validation for the X-ProxyHost and X-Forwarded-Host HTTP request headers based on the nifi.web.proxy.host property. Enabling header validation requires configuring the application with HTTPS. Reverse proxy servers in front of Apache NiFi are responsible for filtering input request headers and providing allowed values to the application.