CVE-2024-24830

CRITICALNVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.7% (51st 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
9.9EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.9Exploit: Elevated riskExposed services: Not assessed

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

OpenObserve is a observability platform built specifically for logs, metrics, traces, analytics, designed to work at petabyte scale. A vulnerability has been identified in the "/api/{org_id}/users" endpoint. This vulnerability allows any authenticated regular user ('member') to add new users with elevated privileges, including the 'root' role, to an organization. This issue circumvents the intended security controls for role assignments. The vulnerability resides in the user creation process, where the payload does not validate the user roles. A regular user can manipulate the payload to assign root-level privileges. This vulnerability leads to Unauthorized Privilege Escalation and significantly compromises the application's role-based access control system. It allows unauthorized control over application resources and poses a risk to data security. All users, particularly those in administrative roles, are impacted. This issue has been addressed in release version 0.8.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/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
Severity99% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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

February 8, 2024

Last Modified

August 27, 2025

Advisory Details (1)

Auto-updated Oct 5, 2026
🔬 Proof of concept available. No fix on record yet. Sources: github.
githubMentions a patch (unverified)🟡 PoC Available

OpenObserve Privilege Escalation Vulnerability in Users API · Advisory · openobserve/openobserve · GitHub

https://github.com/openobserve/openobserve/security/advisories/GHSA-hfxx-g56f-8h5v

Weakness Classification(5)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-24830?
CVE-2024-24830 is a critical vulnerability published on February 8, 2024. OpenObserve is a observability platform built specifically for logs, metrics, traces, analytics, designed to work at petabyte scale. A vulnerability has been identified in the "/api/{org_id}/users" endpoint. This vulnerability allows any authenticated regular user ('member') to add new users with…
When was CVE-2024-24830 disclosed?
CVE-2024-24830 was first published on February 8, 2024, with the most recent update on August 27, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-24830 actively exploited?
CVE-2024-24830 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-24830?
CVE-2024-24830 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2024-24830?
No fix for CVE-2024-24830 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-24830

Explore →

Is Your Infrastructure Affected by CVE-2024-24830?

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

Book a Demo →Browse All CVEs