Openobserve vulnerabilities
We track 6 vulnerabilities in Openobserve products. 6 are rated high or critical, and none are known to be exploited. The most recent was published on November 10, 2026.
Latest Openobserve vulnerabilities
- 9.8 Critical severity
openobserve: Improper Authentication
OpenObserve is a cloud-native observability platform. Prior to 1.1.0, the shared authentication validator in src/api/common/src/auth/validator.rs accepts an empty or whitespace-only HTTP Basic password for an account whose password_ext value is missing or empt
- 7.5 High severity
openobserve: Exposure of Sensitive Information to an Unauthorized Actor
OpenObserve is a cloud-native observability platform. Prior to 0.90.3, OpenObserve registers the /config/runtime endpoint without authentication and serializes the complete server configuration after applying the hide_sensitive_fields keyword filter. The filte
- 7.7 High severity
openobserve: Server-Side Request Forgery
OpenObserve is a cloud-native observability platform. In 0.70.3 and earlier, the validate_enrichment_url function in src/handler/http/request/enrichment_table/mod.rs fails to block IPv6 addresses because Rust's url crate returns them with surrounding brackets
- 8.4 High severity
openobserve: Improper Access Control
OpenObserve is a cloud-native observability platform. Prior to version 0.16.0, organization invitation tokens do not expire once issued, remain valid even after the invited user is removed from the organization, and allow multiple invitations to the same email
- 8.7 High severity
openobserve: Improper Privilege Management
OpenObserve is a cloud-native observability platform. A vulnerability in the user management endpoint `/api/{org_id}/users/{email_id}` allows an "Admin" role user to remove a "Root" user from the organization. This violates the intended privilege hierarchy, en
- 8.8 High severity
openobserve: Improper Privilege Management
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