Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Misconfiguration·Updated Nov 16, 2026

CVE-2026-63645 Scanner

CVE-2026-63645 Scanner - Configuration File Disclosure vulnerability in OpenObserve

Est. Time~10 seconds
Scan TypeGroup Scan
Targetsurl
CostFree
3
Times Used
continuous scan runs
4.3k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
7.5
CVSShigh
Exploitable remotely over the internet · no authentication required.
Description

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 filter does not recognize dsn or creds field names, so meta_postgres_dsn, meta_postgres_ro_dsn, meta_ddl_dsn, and usage_reporting_creds can be returned in plaintext to an unauthenticated network client. PostgreSQL deployments can expose database credentials, and the same response can disclose the root administrator email address, internal NATS address, filesystem layout, and other deployment details. This issue is fixed in version 0.90.3.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
openobserveby openobserve
< 0.90.3
Updated Nov 16, 2026View on NVD →
Detail

OpenObserve is widely used in IT infrastructure to monitor and observe various systems' performance. Administrators and IT professionals commonly deploy it to keep track of system metrics and logs in real-time. The software is essential for identifying and resolving performance bottlenecks and outages. By providing a detailed analysis of system performance, OpenObserve aids in maintaining optimal operations across diverse IT environments. Its ability to correlate events across multiple systems is crucial for comprehensive monitoring. The dependency on OpenObserve for real-time monitoring makes it an indispensable tool in modern infrastructure management.

The vulnerability present in certain versions of OpenObserve allows for the disclosure of sensitive configuration information. This issue arises due to insufficient authentication and access controls on a specific endpoint. As a result, unauthorized users can access server configurations that should be restricted. The exposure includes potentially sensitive information such as database credentials and user email details. By exploiting this weakness, an attacker can gather insights into the configuration, which could facilitate further attacks. It highlights an important flaw in the security posture of the affected OpenObserve versions.

The technical details of the vulnerability involve the /config/runtime endpoint, which is accessible without authentication. It exposes critical configuration data, including PostgreSQL connection strings, in clear text. The vulnerability particularly concerns fields like meta_postgres_dsn and auth.root_user_email, which are not adequately redacted. The use of JSON serialization makes it easier for attackers to extract detailed information. These exposed details can lead to unauthorized access to the metadata database. The lack of endpoint protection emphasizes the need for robust authentication mechanisms.

If exploited, this vulnerability could result in unauthorized access to metadata credentials. Attackers who obtain these credentials may directly access the database and potentially manipulate or extract its data. This could lead to severe breaches of privacy and confidentiality, impacting users and services relying on OpenObserve. There is also the risk of further exploitation within the infrastructure due to the compromised credentials. Such breaches underscore the potential for significant damage to an organization's reputation and operational integrity.

REFERENCES

Solution Advice
  • Upgrade to OpenObserve version 0.90.3 or later to mitigate the vulnerability by removing the /config/runtime route.
  • Implement stronger access controls and authentication mechanisms on critical endpoints.
  • Regularly review and update server configurations to ensure security best practices.
  • Conduct security audits to identify and resolve potential vulnerabilities in the infrastructure.
  • Train your IT team to handle sensitive information securely and respond to configuration exposures efficiently.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.