CVE-2026-25903: Apache NiFi: Missing Authorization of Restricted Permissions for Component Updates
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.75% (FIRST EPSS); higher than 55% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No special conditions are required; it is repeatable.
- Fixed version: Apache Software Foundation Apache NiFi 2.8.0.
Low priority for now. Upgrade to Apache Software Foundation Apache NiFi 2.8.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Apache NiFi 1.1.0 through 2.7.2 are missing authorization when updating configuration properties on extension components that have specific Required Permissions based on the Restricted annotation. The Restricted annotation indicates additional privileges required to add the annotated component to the flow configuration, but framework authorization did not check restricted status when updating a component previously added. The missing authorization requires a more privileged user to add a restricted component to the flow configuration, but permits a less privileged user to make property configuration changes. Apache NiFi installations that do not implement different levels of authorization for Restricted components are not subject to this vulnerability because the framework enforces write permissions as the security boundary. Upgrading to Apache NiFi 2.8.0 is the recommended mitigation.
- Published
- Feb 17, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 55th percentile
- CWE
- CWE-862
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 34 / 40 · 8.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · apache
- 8.7
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/S:P/AU:Y/R:I/V:C/RE:M/U:Amber
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apache | nifi | cpe:2.3:a:apache:nifi |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache nifi1.1.0 and later · before 2.8.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Software Foundation Apache NiFi
- 1.1.0 and later · before 2.8.0affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.apache.nifi:nifi-web-api | from 1.1.0 · before 2.8.0 | 2.8.0 |
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-34468Apache NiFi: Potential Code Injection with Database Services using H254Plan
- CVE-2018-1309Apache NiFi External XML Entity issue in SplitXML processor.40Plan
- CVE-2017-15697A malicious X-ProxyContextPath or X-Forwarded-Context header containing external resources or embedded code could cause remote code executio40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-27017Mar 12, 2025 · Apache NiFi: Potential Insertion of MongoDB Password in Provenance Record27Monitor
- ← EarlierCVE-2025-66524Dec 19, 2025 · Apache NiFi: Deserialization of Untrusted Data in GetAsanaObject Processor30Monitor
- Later →CVE-2026-39816May 8, 2026 · Apache NiFi: Missing Execute Code Required Permission on TinkerpopClientService30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Apache Software Foundation Apache NiFi | 2.8.0 | Vendor (CNA) |
| Maven:org.apache.nifi:nifi-web-api | 2.8.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- David Handermannexceptionfactory.com reported this issue.finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-3981680 days apartApache NiFi: Missing Execute Code Required Permission on TinkerpopClientService30Monitor
- CVE-2026-44914125 days apartApache NiFi: Missing Authorization of Restricted Permissions when Replacing Flow Contents30Monitor
- CVE-2026-68979167 days apartApache NiFi: Missing Authorization for Components Referenced by Parameter Context Updates23Monitor
- CVE-2026-82561211 days apartApache NiFi: Missing Authorization for Components Referenced in Flow Update Methods23Monitor
- CVE-2026-86089211 days apartApache NiFi: Missing Process Group Authorization for Connector Migration9Monitor
- CVE-2026-81866211 days apartApache NiFi: Missing Authorization for Assets and Secrets Referenced by Connector Configuration2Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- A
- Scope
- P
Weakness class (CWE)
CWE-862 · Missing AuthorizationCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:Y/R:I/V:C/RE:M/U:Amber
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.