A flaw was found in the Observability Operator. The Operator creates a ServiceAccount with *ClusterRole* upon deployment of the *Namespace-Scoped* Custom Resource MonitorStack. This issue allows an adversarial Kubernetes Account with only namespaced-level roles, for example, a tenant controlling a namespace, to create a MonitorStack in the authorized namespace and then elevate permission to the cluster level by impersonating the ServiceAccount created by the Operator, resulting in privilege escalation and other issues.
Metrics
Affected Vendors & Products
References
Link | Providers |
---|---|
https://www.cve.org/CVERecord?id=CVE-2025-2843 |
![]() |
History
Fri, 13 Jun 2025 15:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | A flaw was found in the Observability Operator. The Operator creates a ServiceAccount with *ClusterRole* upon deployment of the *Namespace-Scoped* Custom Resource MonitorStack. This issue allows an adversarial Kubernetes Account with only namespaced-level roles, for example, a tenant controlling a namespace, to create a MonitorStack in the authorized namespace and then elevate permission to the cluster level by impersonating the ServiceAccount created by the Operator, resulting in privilege escalation and other issues. | |
Title | observability-operator: Observability Operator privilege escalation | |
Weaknesses | CWE-266 | |
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|

No data.

No data.

No data.
