Authorization Flaw in nifi (CVE-2026-44911)
Summary
Vulnerability in nifi (CVE-2026-44911). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.10.0 or later.
Original description
The description as published by the source.
Authorization handling for component configuration verification requests in Apache NiFi 1.15.0 through 2.9.0 allows clients with read access to submit proposed configuration properties. The proposed properties override current configuration, enabling users with read access to invoke predefined verification methods with alternative settings. Apache NiFi installations that do not implement different levels of authorization for viewing and modifying component configuration are not subject to this vulnerability. Upgrading to Apache NiFi 2.10.0 is the recommended mitigation, requiring write access to submit configuration verification requests.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44911 has been found in nifi.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: upgrade nifi to 2.10.0 or later.
If unsure, ask your IT team or search "nifi CVE-2026-44911" on the vendor's site.
CVE-2026-44911 (nifi) — CWE-863 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.10.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in nifi.
Check the vendor advisory for the affected versions of nifi.
Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.10.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nifi' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'nifi' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nifiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade nifi to 2.10.0ステージング環境で 2.10.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory lists.apache.org
- advisory openwall.com
- web nvd.nist.gov
- web github.com
- web github.com