NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Apache NiFi process group information disclosureGHSA-26p8-xrj2-mv53

MEDIUM

GHSA-26p8-xrj2-mv53 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in org.apache.nifi:nifi-web-api. A fix is available for org.apache.nifi:nifi-web-api — see the affected versions and patch details below.

Also known asCVE-2019-10083
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk
0.69%1.54%2.40%3.25%1.2%2.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.apache.nifi:nifi-web-api☕org.apache.nifi:nifi

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

When updating a Process Group via the API in NiFi versions 1.3.0 to 1.9.2, the response to the request includes all of its contents (at the top most level, not recursively). The response included details about processors and controller services which the user may not have had read access to.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.nifi:nifi-web-api≥ 1.3.0&&< 1.10.01.10.0org.apache.nifi:nifi-web-api:1.10.0
☕Mavenorg.apache.nifi:nifi≥ 1.3.0&&< 1.10.01.10.0org.apache.nifi:nifi:1.10.0

Affected Products

1 product · 1 configurations
Application
nifiapache
≥ 1.3.0 && ≤ 1.9.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.nifi:nifi-web-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.nifi:nifi-web-api to 1.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-26p8-xrj2-mv53 is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

When updating a Process Group via the API in NiFi versions 1.3.0 to 1.9.2, the response to the request includes all of its contents (at the top most level, not recursively). The response included details about processors and controller services which the user may not have had read access to.
O3 Security · Impact-Aware SCA

Is GHSA-26p8-xrj2-mv53 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Apache NiFi process group information disclosure