Kafka UI is an Open-Source Web UI for Apache Kafka Management. Kafka UI API allows users to connect to different Kafka brokers by specifying their network address and port. As a separate feature, it also provides the ability to monitor the performance of Kafka brokers by connecting to their JMX ports. JMX is based on the RMI protocol, so it is inherently susceptible to deserialization attacks. A potential attacker can exploit this feature by connecting Kafka UI backend to its own malicious broker. This vulnerability affects the deployments where one of the following occurs: 1. dynamic.config.enabled property is set in settings. It's not enabled by default, but it's suggested to be enabled in many tutorials for Kafka UI, including its own README.md. OR 2. an attacker has access to the Kafka cluster that is being connected to Kafka UI. In this scenario the attacker can exploit this vulnerability to expand their access and execute code on Kafka UI as well. Instead of setting up a legitimate JMX port, an attacker can create an RMI listener that returns a malicious serialized object for any RMI call. In the worst case it could lead to remote code execution as Kafka UI has the required gadget chains in its classpath. This issue may lead to post-auth remote code execution. This is particularly dangerous as Kafka-UI does not have authentication enabled by default. This issue has been addressed in version 0.7.2. All users are advised to upgrade. There are no known workarounds for this vulnerability. These issues were discovered and reported by the GitHub Security lab and is also tracked as GHSL-2023-230.
CVE-2024-32030
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 8.4 because EPSS predicted 51% probability of exploitation within the next 30 days (98th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 8.1 retained for reference. Confidence: see factors.
Also known asEUVD-2024-29867 (ENISA EUVD)Source: ENISA EUVD
- High exploitation likelihood — EPSS 51%
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 8.1
- EG Score
- 8.4HIGHhigh confidence
- EG Risk
- 62EG Risk 62/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity81% × 45%Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation65% × 40%EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 51%
- EPSS %ILE
- 98th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 8.1 HIGH): a likelihood of exploitation, not impact.
- EG Severity
- 8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 51% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
June 19, 2024
Last Modified
April 15, 2026
Advisory Details (3)
Auto-updated Sep 12, 2026GHSL-2023-229_GHSL-2023-230: Remote code execution (RCE) in UI for Apache Kafka - CVE-2023-52251, CVE-2024-32030 | GitHub Security Lab
https://securitylab.github.com/advisories/GHSL-2023-229_GHSL-2023-230_kafka-ui/added commons-collections4 library instead of commons-collections
Patch available: provectus/kafka-ui v0.7.2 (PR #4427 merged 2024-04-08)
https://github.com/provectus/kafka-ui/pull/4427commit 83b5a60cc085 (provectus/kafka-ui)
Patch available: provectus/kafka-ui v0.7.2 (contains commit 83b5a60cc085)
https://github.com/provectus/kafka-ui/commit/83b5a60cc08501b570a0c4d0b4cdfceb1b88d6b7#diff-37e769f4709c1e78c076a5949bbcead74e969725bfd89c7c4ba6d6f229a411e6R36Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 34× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 92 of 178 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 8 repeat rows among the latest 100 are merged into the row they repeat. The 86 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-31 16:30 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-30 16:32 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-29 16:30 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-28 16:29 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-28 07:36 UTCEG score recompute
- 2026-10-27 16:29 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-26 16:29 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-25 17:12 UTCEG score recompute
- 2026-10-25 16:30 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-24 16:30 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-23 16:29 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-22 16:31 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-20 19:59 UTCEG score recompute
- 2026-10-20 16:30 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-19 16:29 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-18 07:17 UTCEG score recompute
- 2026-10-17 16:30 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-16 16:36 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-15 16:30 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-14 16:30 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-13 16:30 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-12 17:55 UTCEG score recompute
- 2026-10-12 16:31 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-11 21:20 UTCEG score recompute
Show 67 moreShow fewer
- 2026-10-11 16:13 UTCEG score recompute▲ 0.10
- 2026-10-11 13:46 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-10 19:58 UTCEPSS rescoreEPSS 51% · 98th percentile
- 2026-10-09 20:05 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-10-08 17:07 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-10-07 10:24 UTCOSV refresh
- 2026-10-06 15:15 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-10-03 14:24 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-10-01 19:48 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-09-30 19:43 UTCEG score recompute▲ 0.10
- 2026-09-30 15:01 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-09-27 13:43 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-09-26 15:57 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-09-26 00:23 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-09-23 13:46 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-09-22 14:46 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-09-19 15:40 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-09-18 19:26 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-09-17 16:06 UTCOSV refresh
- 2026-09-16 14:06 UTCEPSS rescoreEPSS 39% · 98th percentile
- 2026-09-15 03:08 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-09-12 14:59 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-09-11 14:51 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-09-11 09:35 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-09-08 21:58 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-09-06 13:46 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-09-05 15:26 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-09-04 13:58 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-09-04 05:05 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-09-02 14:10 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-09-01 13:52 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-30 19:15 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-30 01:20 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-29 16:43 UTCOSV refresh
- 2026-08-28 21:39 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-27 14:23 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-26 14:44 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-25 13:47 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-24 14:15 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-21 23:47 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-20 22:53 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-19 17:02 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-18 13:46 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-16 14:54 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-15 01:28 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-13 21:59 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-13 04:00 UTCOSV refresh
- 2026-08-12 13:49 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-11 13:40 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-10 23:58 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-08 16:35 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-07 16:25 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-06 13:45 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-04 15:08 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-04 10:36 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-01 04:14 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-30 16:26 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-30 01:29 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-28 15:34 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-28 12:20 UTCOSV refresh
- 2026-07-26 14:53 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-25 14:16 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-24 14:16 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-23 02:36 UTCEG score recompute▲ 0.10
Related CVEs(same CWE)
Same CWE
10 shownCWE-94 · CWE-502
Frequently asked(5)
What is CVE-2024-32030?
When was the CVE record for CVE-2024-32030 published?
Is CVE-2024-32030 actively exploited?
What is the CVSS score of CVE-2024-32030?
How do I remediate CVE-2024-32030?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2024-32030
Is Your Infrastructure Affected by CVE-2024-32030?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.