CVE-2026-87976

HIGHNVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Apache NiFi Registry 0.4.0 through 2.11.0 are subject to path manipulation when storing extension bundle content using group, artifact, and version coordinates from uploaded NAR manifests. The default file persistence provider used coordinates as filesystem path components without rejected parent-directory names, and the path-containment check compared an unnormalized resolved path. An authenticated user authorized to write and delete bundles in a bucket can upload a NAR with a crafted manifest resulting in file system operations outside of the file persistence directory. Upgrading to Apache NiFi Registry 2.12.0 is the recommended mitigation, which rejects parent-directory coordinates and requires a normalized path to remain a strict child of the storage root location.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 21, 2026

Advisory Details (1)

Auto-updated Sep 16, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-87976(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 29× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-25 07:15 UTCGHSA enrichment
  2. 2026-09-24 18:34 UTCEG score recompute
  3. 2026-09-24 18:34 UTCGHSA enrichment
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-24 05:53 UTCEG score recompute
  6. 2026-09-24 05:53 UTCGHSA enrichment
  7. 2026-09-23 17:54 UTCEPSS rescore
  8. 2026-09-23 17:11 UTCGHSA enrichment
  9. 2026-09-23 04:26 UTCEG score recompute
  10. 2026-09-23 04:26 UTCGHSA enrichment
  11. 2026-09-22 16:01 UTCEPSS rescore
  12. 2026-09-22 15:44 UTCGHSA enrichment
  13. 2026-09-22 03:02 UTCEG score recompute
  14. 2026-09-22 03:02 UTCGHSA enrichment
  15. 2026-09-21 21:09 UTCEPSS rescore
  16. 2026-09-21 14:20 UTCEG score recompute▲ 0.90
  17. 2026-09-21 14:20 UTCGHSA enrichment
  18. 2026-09-21 14:20 UTCNVD updateCVSS v3 → 8.1
  19. 2026-09-21 13:35 UTCGHSA enrichment
  20. 2026-09-21 00:54 UTCEG score recompute
  21. 2026-09-21 00:54 UTCGHSA enrichment
  22. 2026-09-20 20:16 UTCEPSS rescore
  23. 2026-09-20 12:12 UTCGHSA enrichment
  24. 2026-09-19 23:24 UTCEG score recompute
  25. 2026-09-19 23:24 UTCGHSA enrichment
Show 14 more
  1. 2026-09-19 10:43 UTCGHSA enrichment
  2. 2026-09-18 21:51 UTCEG score recompute
  3. 2026-09-18 21:51 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 09:10 UTCGHSA enrichment
  6. 2026-09-17 20:28 UTCEG score recompute
  7. 2026-09-17 20:28 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-17 19:20 UTCEG score recompute
  10. 2026-09-17 19:20 UTCGHSA enrichment
  11. 2026-09-17 10:09 UTCGHSA enrichment
  12. 2026-09-16 21:00 UTCEG score recompute
  13. 2026-09-16 19:44 UTCEG score recompute
  14. 2026-09-16 19:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-87976?
CVE-2026-87976 is a high vulnerability published on September 16, 2026. Apache NiFi Registry 0.4.0 through 2.11.0 are subject to path manipulation when storing extension bundle content using group, artifact, and version coordinates from uploaded NAR manifests. The default file persistence provider used coordinates as filesystem path components without rejected…
When was CVE-2026-87976 disclosed?
CVE-2026-87976 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-87976 actively exploited?
CVE-2026-87976 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 45.7% of all scored CVEs.
What is the CVSS score of CVE-2026-87976?
CVE-2026-87976 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-87976?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-87976, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-87976

Explore →

Is Your Infrastructure Affected by CVE-2026-87976?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.