CVE-2024-25106

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2024-22468 (ENISA EUVD)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

OpenObserve is a observability platform built specifically for logs, metrics, traces, analytics, designed to work at petabyte scale. A critical vulnerability has been identified in the "/api/{org_id}/users/{email_id}" endpoint. This vulnerability allows any authenticated user within an organization to remove any other user from that same organization, irrespective of their respective roles. This includes the ability to remove users with "Admin" and "Root" roles. By enabling any organizational member to unilaterally alter the user base, it opens the door to unauthorized access and can cause considerable disruptions in operations. The core of the vulnerability lies in the remove_user_from_org function in the user management system. This function is designed to allow organizational users to remove members from their organization. The function does not check if the user initiating the request has the appropriate administrative privileges to remove a user. Any user who is part of the organization, irrespective of their role, can remove any other user, including those with higher privileges. This vulnerability is categorized as an Authorization issue leading to Unauthorized User Removal. The impact is severe, as it compromises the integrity of user management within organizations. By exploiting this vulnerability, any user within an organization, without the need for administrative privileges, can remove critical users, including "Admins" and "Root" users. This could result in unauthorized system access, administrative lockout, or operational disruptions. Given that user accounts are typically created by "Admins" or "Root" users, this vulnerability can be exploited by any user who has been granted access to an organization, thereby posing a critical risk to the security and operational stability of the application. This issue has been addressed in release version 0.8.0. Users are advised to upgrade.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
42nd
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

February 8, 2024

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Aug 2, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

OpenObserve Unauthorized Access Vulnerability in Users API · Advisory · openobserve/openobserve · GitHub

https://github.com/openobserve/openobserve/security/advisories/GHSA-3m5f-9m66-xgp7

Weakness Classification(5)

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 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 251 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 151 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-25106?
CVE-2024-25106 is a critical-severity vulnerability; its CVE record was published on February 8, 2024. OpenObserve is a observability platform built specifically for logs, metrics, traces, analytics, designed to work at petabyte scale. A critical vulnerability has been identified in the "/api/{org_id}/users/{email_id}" endpoint. This vulnerability allows any authenticated user within an organization…
When was the CVE record for CVE-2024-25106 published?
The CVE record for CVE-2024-25106 was published on February 8, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2024-25106 actively exploited?
CVE-2024-25106 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-25106?
CVE-2024-25106 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2024-25106?
The CVE record for CVE-2024-25106 names the fix: "This issue has been addressed in release version 0.8.0."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-25106?

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

Book a Demo →Browse All CVEs