# CVE-2024-24830: OpenObserve Privilege Escalation Vulnerability in Users API

> Authenticated regular users can escalate privileges to root by manipulating user creation payloads, compromising access controls.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2024
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-hfxx-g56f-8h5v

## What is CVE-2024-24830?

CVE-2024-24830 is a critical vulnerability in openobserve, published on 8 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication), CWE-284 (Improper Access Control), CWE-272 (Least Privilege Violation), CWE-285 (Improper Authorization), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-24830?

It affects 1 product.


Products: Openobserve Openobserve.

## How do I fix CVE-2024-24830?

No fix has been published for CVE-2024-24830 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-24830 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24830 exists.

## Other vulnerabilities in openobserve

- [CVE-2024-25106](https://insights.sbomify.com/CVE-2024-25106/): OpenObserve Unauthorized Access Vulnerability in Users API (critical 9.1)
- [CVE-2024-41808](https://insights.sbomify.com/CVE-2024-41808/): OpenObserve stored XSS vulnerability may lead to complete account takeover (high 8.8)
- [CVE-2026-39361](https://insights.sbomify.com/CVE-2026-39361/): OpenObserve has a SSRF Protection Bypass via IPv6 Bracket Notation in validate_enrichment_url (high 7.7)
- [CVE-2024-41809](https://insights.sbomify.com/CVE-2024-41809/): OpenObserve Cross-site Scripting (XSS) vulnerability in `openobserve/web/src/views/MemberSubscription.vue` (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-24830 and fix it if it is affected.

What it is: CVE-2024-24830 is a critical vulnerability in openobserve, published on 8 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24830 exists.

Affected product: openobserve. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-24830/ (Markdown: https://insights.sbomify.com/CVE-2024-24830/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-24830
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-24830
- OSV: https://osv.dev/vulnerability/CVE-2024-24830

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-24830/
Summaries are generated and may contain mistakes; the official description above is the record.