Skip to content
NewA calmer, faster ZeroHour

CVE-2026-87976: Apache NiFi Registry: Improper Limitation of Pathname in Persisted Extension Bundles

oss-security ()2
Part of a story covered by 5 sourcesCVE-2026-70469: Apache NiFi: Improper Handling of Case Sensitivity for Content-Encoding in HTTP RequestsMerged summary & timeline
AI summary · glm-5.3-flashSummaries by Vani AI

Apache NiFi Registry 0.4.0-2.11.0 allows path manipulation when storing extension bundle content from uploaded NAR manifests (CVE-2026-87976, High).

Apache NiFi Registry versions 0.4.0 through 2.11.0 are affected by improper limitation of a pathname (CVE-2026-87976), rated High severity by the maintainers. When storing extension bundle content, the default file persistence provider used group, artifact, and version coordinates from uploaded NAR manifests as filesystem path components without sufficient validation. The disclosure was posted by Apache NiFi maintainer David Handermann on the oss-security mailing list.

Key facts
  • Affects Apache NiFi Registry 0.4.0 through 2.11.0 (nifi-registry-framework artifact)
  • Path manipulation occurs via group, artifact, and version coordinates from NAR manifests
  • Default file persistence provider lacks pathname validation
  • Rated High severity in the official Apache disclosure
Analyze CVE-2026-87976 with Vani AIImpact, affected versions, exploitation, mitigations and detection

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2026-87976
Authenticated path traversal in Apache NiFi Registry extension bundle storage
7.2—

From the original article

Posted by David Handermann on Sep 16 Severity: High Affected versions: - Apache NiFi Registry (org. apache. nifi.

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.