How severe is CVE-2022-33140?

CVE-2022-33140 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-33140?

CVE-2022-33140 affects the following packages: org.apache.nifi.registry:nifi-registry-core (Maven), org.apache.nifi:nifi (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-33140?

Update org.apache.nifi.registry:nifi-registry-core to 1.16.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-33140 is resolved across your whole dependency graph.

How do I detect CVE-2022-33140 in my Maven dependencies?

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

How do I mitigate CVE-2022-33140 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2022-33140 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-33140 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-33140?

CVE-2022-33140 has an EPSS (Exploit Prediction Scoring System) score of 3.7%, placing it in the 90th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-33140?

CVE-2022-33140 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-33140 published, and has it been updated?

CVE-2022-33140 was published on June 15, 2022 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2022-33140 — nifi-registry-core

HIGH

CVE-2022-33140 is a high-severity (CVSS 8.8) OS Command Injection vulnerability in org.apache.nifi.registry:nifi-registry-core. A fix is available for org.apache.nifi.registry:nifi-registry-core — see the affected versions and patch details below.

Code injection in Apache NiFi and NiFi Registry

Also known asBIT-nifi-2022-33140GHSA-77hf-23pq-2g7c

Published

Jun 15, 2022

Updated

Apr 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

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.registry:nifi-registry-core☕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

The optional ShellUserGroupProvider in Apache NiFi 1.10.0 to 1.16.2 and Apache NiFi Registry 0.6.0 to 1.16.2 does not neutralize arguments for group resolution commands, allowing injection of operating system commands on Linux and macOS platforms. The ShellUserGroupProvider is not included in the default configuration. Command injection requires ShellUserGroupProvider to be one of the enabled User Group Providers in the Authorizers configuration. Command injection also requires an authenticated user with elevated privileges. Apache NiFi requires an authenticated user with authorization to modify access policies in order to execute the command. Apache NiFi Registry requires an authenticated user with authorization to read user groups in order to execute the command. The resolution removes command formatting based on user-provided arguments.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.nifi.registry:nifi-registry-core`	≥ 0.6.0&&< 1.16.3	1.16.3`org.apache.nifi.registry:nifi-registry-core:1.16.3`
☕Maven	`org.apache.nifi:nifi`	≥ 1.10.0&&< 1.16.3	1.16.3`org.apache.nifi:nifi:1.16.3`

Affected Products

2 products · 2 configurations

Application

nifiapache

≥ 1.10.0 && ≤ 1.16.2

range

Application

nifi registryapache

≥ 0.6.0 && ≤ 1.16.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.nifi.registry:nifi-registry-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.nifi.registry:nifi-registry-core to 1.16.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-33140 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-33140 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-78OS Command Injection

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

nifi

7.0/10

Code-Review10/10

Maintained10/10

Branch-ProtectionN/A

Assessed Oct 26, 2026

Timeline

Disclosed

Jun 15, 2022

Last updated

Apr 10, 2026

Identifiers

CVE-2022-33140

GHSA-77hf-23pq-2g7c

BIT-nifi-2022-33140

References

Advisorylists.apache.org · bzs2pcdjsdrh5039oslmfr9mbs9qqdhr Advisorynvd.nist.gov · CVE 2022 33140 Reportnifi.apache.org · security Packagegithub.com · nifi

Related vulnerabilities

This CVE is high severity; 5 of 8 other CVEs affecting nifi are rated as high or higher (top: critical).

CVE-2017-5636CVE-2017-7667CVE-2017-7665CVE-2017-12623CVE-2017-15697CVE-2016-8748CVE-2018-1310CVE-2017-12632

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedApr 10, 2026

CVE-2022-33140 — nifi-registry-core

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-33140 in your dependencies?