CVE-2024-36111

MEDIUMNVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under NVD CVSS v3. EPSS exploit probability: 8.4% (94th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 8.4%CVSS: 6.3Exploit: Elevated riskExposed services: Not assessed

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

KubePi is a K8s panel. Starting in version 1.6.3 and prior to version 1.8.0, there is a defect in the KubePi JWT token verification. The JWT key in the default configuration file is empty. Although a random 32-bit string will be generated to overwrite the key in the configuration file when the key is detected to be empty in the configuration file reading logic, the key is empty during actual verification. Using an empty key to generate a JWT token can bypass the login verification and directly take over the back end. Version 1.8.0 contains a patch for this issue.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100CISA SSVC

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
Severity63% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
8.4%
EPSS %ILE
94th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 25, 2024

Last Modified

April 15, 2026

References (2)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 31× 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.

Showing the most recent 100 of 193 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-36111?
CVE-2024-36111 is a medium vulnerability published on July 25, 2024. KubePi is a K8s panel. Starting in version 1.6.3 and prior to version 1.8.0, there is a defect in the KubePi JWT token verification. The JWT key in the default configuration file is empty. Although a random 32-bit string will be generated to overwrite the key in the configuration file when the key…
When was CVE-2024-36111 disclosed?
CVE-2024-36111 was first published on July 25, 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-36111 actively exploited?
CVE-2024-36111 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.4% probability of exploitation in the next 30 days (94th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-36111?
CVE-2024-36111 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2024-36111?
No fix for CVE-2024-36111 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-36111?

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

Book a Demo →Browse All CVEs