CVE-2022-34916 | Improper Input Validation (JNDI Injection) in JMSMessageConsumer

Apache Flume versions 1.4.0 through 1.10.0 are vulnerable to a remote code execution (RCE) attack when a configuration uses a JMS Source with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI to allow only the use of the java protocol or no protocol.

Published: 2022-08-21 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-34916 is rated High Risk (67.7/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 2.31%). High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-34916

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-21 2.23% 2.31% +0.08%
2 2026-06-15 2.66% 2.23% -0.43%
3 2025-09-01 — 2.66% —

Full EPSS history (19 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-34916

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]

Weakness enumeration for CVE-2022-34916

GitHub Security Advisory for CVE-2022-34916

GHSA-h9mh-mgpv-gqmv · Severity: critical · Ecosystem: maven — Remote code execution in Apache Flume

OS Trackers for CVE-2022-34916

vendor priority summary link
redhat high — https://access.redhat.com/security/cve/CVE-2022-34916

Affected software / configurations for CVE-2022-34916

Vendor Product Version Raw CPE
apache flume >= 1.4.0, < 1.10.1 cpe:2.3:a:apache:flume:*:*:*:*:*:*:*:*

References for CVE-2022-34916

URL Tags
https://issues.apache.org/jira/browse/FLUME-3428 Issue Tracking Vendor Advisory
https://lists.apache.org/thread/qkmt4r2t9tbrxrdbjg1m2oczbvczd9zn Mailing List Patch Vendor Advisory
cvelogic Threat Intelligence