How severe is CVE-2023-36542?

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

Which packages are affected by CVE-2023-36542?

CVE-2023-36542 affects the following packages: org.apache.nifi:nifi-cdc-mysql-bundle (Maven), org.apache.nifi:nifi-jms-processors (Maven), org.apache.nifi:nifi-standard-processors (Maven), org.apache.nifi:nifi-dbcp-service (Maven), org.apache.nifi:nifi-hikari-dbcp-service (Maven), org.apache.nifi:nifi-hadoop-dbcp-service (Maven), org.apache.nifi:nifi-hbase_2-client-service (Maven), org.apache.nifi:nifi-record-serialization-services (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-36542?

Update org.apache.nifi:nifi-cdc-mysql-bundle to 1.23.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-36542 is resolved across your whole dependency graph.

How do I detect CVE-2023-36542 in my Maven dependencies?

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

How do I mitigate CVE-2023-36542 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-2023-36542 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2023-36542, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-36542?

CVE-2023-36542 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 80th 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-2023-36542?

CVE-2023-36542 is classified as Code Injection (CWE-94). 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-2023-36542 published, and has it been updated?

CVE-2023-36542 was published on July 29, 2023 and was last updated on October 28, 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-2023-36542 — nifi-cdc-mysql-bundle

HIGHFix: apache/nifi@5325787

CVE-2023-36542 is a high-severity (CVSS 8.8) Code Injection vulnerability in org.apache.nifi:nifi-cdc-mysql-bundle. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.apache.nifi:nifi-cdc-mysql-bundle — see the affected versions and patch details below.

Apache NiFi: Potential Code Injection with Properties Referencing Remote Resources

Also known asBIT-nifi-2023-36542GHSA-r969-8v3h-23v9

Published

Jul 29, 2023

Updated

Oct 28, 2026

Affected

8 pkgs

Patched

8 / 8

Exploits

1 known

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-36542.

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% 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

8 pkgs affected

☕org.apache.nifi:nifi-cdc-mysql-bundle☕org.apache.nifi:nifi-jms-processors☕org.apache.nifi:nifi-standard-processors☕org.apache.nifi:nifi-dbcp-service☕org.apache.nifi:nifi-hikari-dbcp-service☕org.apache.nifi:nifi-hadoop-dbcp-service☕org.apache.nifi:nifi-hbase_2-client-service☕org.apache.nifi:nifi-record-serialization-services

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

Apache NiFi 0.0.2 through 1.22.0 include Processors and Controller Services that support HTTP URL references for retrieving drivers, which allows an authenticated and authorized user to configure a location that enables custom code execution. The resolution introduces a new Required Permission for referencing remote resources, restricting configuration of these components to privileged users. The permission prevents unprivileged users from configuring Processors and Controller Services annotated with the new Reference Remote Resources restriction. Upgrading to Apache NiFi 1.23.0 is the recommended mitigation.

Affected Packages

8 total 8 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.nifi:nifi-cdc-mysql-bundle`	≥ 0.0.2&&< 1.23.0	1.23.0`org.apache.nifi:nifi-cdc-mysql-bundle:1.23.0`
☕Maven	`org.apache.nifi:nifi-jms-processors`	≥ 0.0.2&&< 1.23.0	1.23.0`org.apache.nifi:nifi-jms-processors:1.23.0`
☕Maven	`org.apache.nifi:nifi-standard-processors`	≥ 0.0.2&&< 1.23.0	1.23.0`org.apache.nifi:nifi-standard-processors:1.23.0`
☕Maven	`org.apache.nifi:nifi-dbcp-service`	≥ 0.0.2&&< 1.23.0	1.23.0`org.apache.nifi:nifi-dbcp-service:1.23.0`
☕Maven	`org.apache.nifi:nifi-hikari-dbcp-service`	≥ 0.0.2&&< 1.23.0	1.23.0`org.apache.nifi:nifi-hikari-dbcp-service:1.23.0`
☕Maven	`org.apache.nifi:nifi-hadoop-dbcp-service`	≥ 0.0.2&&< 1.23.0	1.23.0`org.apache.nifi:nifi-hadoop-dbcp-service:1.23.0`

Affected Products

1 product · 1 configurations

Application

nifiapache

≥ 0.0.2 && ≤ 1.22.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Apache NiFi 0.0.2 through 1.22.0 include Processors and Controller Servi…

media.defense.govAPISep 2024

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:nifi-cdc-mysql-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.nifi:nifi-cdc-mysql-bundle to 1.23.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-36542 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-2023-36542 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-94Code Injection

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Jul 29, 2023

First exploit

Sep 18, 2024

Last updated

Oct 28, 2026

Identifiers

CVE-2023-36542

GHSA-r969-8v3h-23v9

BIT-nifi-2023-36542

References

Advisorygithub.com · CVE 2023 36542.json Advisorylists.apache.org · swnly3dzhhq9zo3rofc8djq77stkhbof Advisorynifi.apache.org · security Advisorynvd.nist.gov · CVE 2023 36542 Webseclists.org Webopenwall.com Webgithub.com · 532578799c Webissues.apache.org · NIFI 11744 Packagegithub.com · nifi

Related vulnerabilities

Also affects nifi-jms-processors

This CVE is high severity — higher than any of the other 2 CVEs affecting nifi-jms-processors (highest there: moderate).

CVE-2023-40037CVE-2023-34212

Also affects nifi-standard-processors

This CVE is high severity; 1 of 1 other CVE affecting nifi-standard-processors is rated as high or higher (top: critical).

CVE-2018-1309

Same weakness: CWE-94

This CVE is high severity; 5 of 5 other CVEs with CWE-94 are rated as high or higher (top: critical).

CVE-2026-63469CVE-2026-63470CVE-2026-63471CVE-2026-62284CVE-2026-61536Browse all CWE-94

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2023-36542 — nifi-cdc-mysql-bundle

Exploitation Status

No confirmed exploitation observed yet

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-2023-36542 in your dependencies?