CVE-2024-32030

HIGHNVD 8.18.2▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.2 because EPSS predicts 34% probability of exploitation within the next 30 days (top 1.8% of all CVEs). NVD baseline CVSS 8.1 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 34%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.2(high)
EG Risk
53(Track*)
EG Risk 53/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
98.2%
KEV
Not listed

Published

June 19, 2024

Last Modified

April 15, 2026

References (6)

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-24 14:16 UTCEPSS rescore
  2. 2026-07-23 02:36 UTCEG score recompute▲ 0.10
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-21 15:23 UTCEPSS rescore
  5. 2026-07-20 17:06 UTCEPSS rescore
  6. 2026-07-19 02:28 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:03 UTCEPSS rescore
  9. 2026-07-18 10:03 UTCEPSS rescore
  10. 2026-07-16 17:01 UTCEPSS rescore
  11. 2026-07-15 16:56 UTCEPSS rescore
  12. 2026-07-15 16:56 UTCEPSS rescore
  13. 2026-07-15 01:59 UTCEPSS rescore
  14. 2026-07-15 01:59 UTCEPSS rescore
  15. 2026-07-13 22:28 UTCEPSS rescore
  16. 2026-07-13 06:11 UTCEPSS rescore
  17. 2026-07-12 05:45 UTCEPSS rescore
  18. 2026-07-11 08:26 UTCEPSS rescore
  19. 2026-07-11 08:26 UTCEPSS rescore
  20. 2026-07-11 04:11 UTCOSV refresh
  21. 2026-07-09 19:09 UTCEPSS rescore
  22. 2026-07-08 15:13 UTCEPSS rescore
  23. 2026-07-06 16:26 UTCEPSS rescore
  24. 2026-07-06 16:26 UTCEPSS rescore
  25. 2026-07-05 02:29 UTCEPSS rescore
Show 63 more
  1. 2026-07-04 06:30 UTCEPSS rescore
  2. 2026-07-02 17:00 UTCEPSS rescore
  3. 2026-07-01 15:05 UTCEPSS rescore
  4. 2026-06-28 04:55 UTCEPSS rescore
  5. 2026-06-28 04:55 UTCEPSS rescore
  6. 2026-06-27 03:07 UTCEPSS rescore
  7. 2026-06-27 03:07 UTCEPSS rescore
  8. 2026-06-25 13:49 UTCEPSS rescore
  9. 2026-06-25 13:48 UTCEPSS rescore
  10. 2026-06-24 14:04 UTCEPSS rescore
  11. 2026-06-24 14:04 UTCEPSS rescore
  12. 2026-06-23 21:32 UTCEPSS rescore
  13. 2026-06-23 21:32 UTCEPSS rescore
  14. 2026-06-22 11:04 UTCOSV refresh
  15. 2026-06-21 01:58 UTCEPSS rescore
  16. 2026-06-21 01:58 UTCEPSS rescore
  17. 2026-06-18 17:51 UTCEPSS rescore
  18. 2026-06-18 17:51 UTCEPSS rescore
  19. 2026-06-17 17:52 UTCEPSS rescore
  20. 2026-06-17 17:52 UTCEPSS rescore
  21. 2026-06-16 17:52 UTCEPSS rescore
  22. 2026-06-16 17:51 UTCEPSS rescore
  23. 2026-06-15 17:47 UTCEPSS rescore
  24. 2026-06-12 23:11 UTCEPSS rescore
  25. 2026-06-12 23:11 UTCEPSS rescore
  26. 2026-06-11 13:59 UTCEPSS rescore
  27. 2026-06-10 22:17 UTCEPSS rescore
  28. 2026-06-07 15:24 UTCEPSS rescore
  29. 2026-06-07 15:24 UTCEPSS rescore
  30. 2026-06-06 13:46 UTCEPSS rescore
  31. 2026-06-06 13:46 UTCEPSS rescore
  32. 2026-06-05 22:46 UTCEPSS rescore
  33. 2026-06-05 22:46 UTCEPSS rescore
  34. 2026-06-04 16:09 UTCOSV refresh
  35. 2026-06-04 13:11 UTCEPSS rescore
  36. 2026-06-04 13:11 UTCEPSS rescore
  37. 2026-06-04 13:11 UTCEPSS rescore
  38. 2026-06-02 20:12 UTCEPSS rescore
  39. 2026-06-02 20:12 UTCEPSS rescore
  40. 2026-05-31 00:15 UTCEPSS rescore
  41. 2026-05-31 00:15 UTCEPSS rescore
  42. 2026-05-28 13:44 UTCEPSS rescore
  43. 2026-05-28 13:44 UTCEPSS rescore
  44. 2026-05-28 13:44 UTCEPSS rescore
  45. 2026-05-27 13:40 UTCEPSS rescore
  46. 2026-05-27 13:40 UTCEPSS rescore
  47. 2026-05-26 07:18 UTCEPSS rescore
  48. 2026-05-26 07:18 UTCEPSS rescore
  49. 2026-05-22 21:16 UTCEPSS rescore
  50. 2026-05-22 21:16 UTCEPSS rescore
  51. 2026-05-22 21:16 UTCEPSS rescore
  52. 2026-05-22 21:16 UTCEPSS rescore
  53. 2026-05-22 00:49 UTCEG score recompute
  54. 2026-05-20 22:37 UTCEPSS rescore
  55. 2026-05-20 22:37 UTCEPSS rescore
  56. 2026-05-20 22:37 UTCEPSS rescore
  57. 2026-05-20 22:37 UTCEPSS rescore
  58. 2026-05-20 22:37 UTCEPSS rescore
  59. 2026-05-18 21:30 UTCEPSS rescore
  60. 2026-05-18 21:30 UTCEPSS rescore
  61. 2026-05-18 21:30 UTCEPSS rescore
  62. 2026-05-18 21:30 UTCEPSS rescore
  63. 2026-05-18 21:30 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-32030?
CVE-2024-32030 is a high vulnerability published on June 19, 2024. 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…
When was CVE-2024-32030 disclosed?
CVE-2024-32030 was first published in the National Vulnerability Database on June 19, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-32030 actively exploited?
CVE-2024-32030 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-32030?
CVE-2024-32030 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.2.
How do I remediate CVE-2024-32030?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-32030, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-32030

Explore →

Is Your Infrastructure Affected by CVE-2024-32030?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs