Description
Apache NiFI 1.10.0 through 2.10.0 provide a Parameter Context update REST API method that does not enforce authorization checking on components referencing Parameter values. Updating a Parameter Context can change parameter values that affect referencing components, but framework authorization was limited to read and write privileges on the Parameter Context itself. As a result of the missing authorization, an authenticated user authorized to modify a Parameter Context, but not authorized on referencing components, could alter Parameter values affecting those components. In deployments where a Parameter value contains executable scripting content, updating a Parameter can result in code execution during automatic component validation, without starting the referencing component. The impact was limited to stopped components by existing verification checks, and the issue applies only to deployments that use component-level authorization policies. Upgrading to Apache NiFi 2.11.0 is the recommended mitigation, which aligns the Parameter Context update method authorization with other methods, adding authorization checking on affected components.
Published: 2026-08-03
Score: 5.9 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Apache NiFi versions 1.10.0 through 2.10.0 expose a Parameter Context update REST endpoint that does not enforce component‑level authorization. An authenticated user with write rights on a Parameter Context can modify parameter values that are referenced by other components, even if the user lacks permission to modify those components. If the parameter contains executable script content, the change triggers code execution during component validation, although the affected component remains stopped.

Affected Systems

Affected systems are deployments of Apache NiFi produced by the Apache Software Foundation, specifically versions 1.10.0 to 2.10.0 inclusive. The vulnerability does not apply to releases newer than 2.10.0.

Risk and Exploitability

The CVSS score of 5.9 indicates a moderate severity. No EPSS score is available and the issue is not listed in CISA’s KEV catalog, suggesting a lower likelihood of widespread exploitation. The attack requires an authenticated user who can alter a Parameter Context; if the user does not have write access to the referenced components, the exploitation still allows unauthorized modification of parameter values and potential code execution during validation, but does not affect running components.

Generated by OpenCVE AI on August 4, 2026 at 09:52 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Apache NiFi to version 2.11.0 or later to enforce component‑level authorization on Parameter Context updates.
  • Limit write permissions on Parameter Contexts to trusted users only, ensuring that users who can modify parameters also have appropriate access to referenced components.
  • If executable scripting is used in parameters, consider disabling it or using stricter execution policies to prevent unintended code execution during validation.

Generated by OpenCVE AI on August 4, 2026 at 09:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 05 Aug 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 04 Aug 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 04 Aug 2026 00:45:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache nifi
Vendors & Products Apache
Apache nifi

Mon, 03 Aug 2026 20:15:00 +0000

Type Values Removed Values Added
Description Apache NiFI 1.10.0 through 2.10.0 provide a Parameter Context update REST API method that does not enforce authorization checking on components referencing Parameter values. Updating a Parameter Context can change parameter values that affect referencing components, but framework authorization was limited to read and write privileges on the Parameter Context itself. As a result of the missing authorization, an authenticated user authorized to modify a Parameter Context, but not authorized on referencing components, could alter Parameter values affecting those components. In deployments where a Parameter value contains executable scripting content, updating a Parameter can result in code execution during automatic component validation, without starting the referencing component. The impact was limited to stopped components by existing verification checks, and the issue applies only to deployments that use component-level authorization policies. Upgrading to Apache NiFi 2.11.0 is the recommended mitigation, which aligns the Parameter Context update method authorization with other methods, adding authorization checking on affected components.
Title Apache NiFi: Missing Authorization for Components Referenced by Parameter Context Updates
Weaknesses CWE-862
References
Metrics cvssV4_0

{'score': 5.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:H/VA:L/SC:L/SI:L/SA:L/S:N/AU:Y/R:U/V:C/RE:L/U:Clear'}


cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-08-05T13:33:59.526Z

Reserved: 2026-08-01T20:11:39.050Z

Link: CVE-2026-68979

cve-icon Vulnrichment

Updated: 2026-08-03T21:25:17.070Z

cve-icon NVD

Status : Analyzed

Published: 2026-08-03T20:17:28.977

Modified: 2026-08-05T14:59:03.460

Link: CVE-2026-68979

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-04T10:00:04Z

Weaknesses