CVE-2026-54665
Apache NiFi: Missing Validation for Proxy Host Headers
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.
| CWE | CWE-346 |
| Vendor | apache software foundation |
| Product | apache nifi |
| Published | Jun 22, 2026 |
| Last Updated | Jun 22, 2026 |
Get instant alerts for apache software foundation apache nifi
Be the first to know when new unknown vulnerabilities affecting apache software foundation apache nifi are published — delivered to Slack, Telegram or Discord.