CVE-2025-2843
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Observability Operator creates a ServiceAccount with a ClusterRole when deploying namespace-scoped MonitorStack resources. A tenant with only namespace-level permissions can create a MonitorStack in their authorized namespace and impersonate this ServiceAccount to gain cluster-level privileges, achieving privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Observability Operator installationRun 'kubectl get pods -A | grep -i observability' or check if the 'monitorstacks' CRD exists with 'kubectl get crd monitorstacks'Affected if The operator is installed and the MonitorStack CRD exists in the cluster
-
Find MonitorStack custom resourcesRun 'kubectl get monitorstacks --all-namespaces' to list any deployed MonitorStack instancesAffected if Any MonitorStack resource exists in any namespace, which triggers the operator to create a privileged ServiceAccount
-
Locate operator-created ServiceAccountsRun 'kubectl get serviceaccounts -A | grep -E "(monitor|observability)"' to find ServiceAccounts created by the operator, then check which namespace they belong to with 'kubectl get serviceaccount <name> -n <namespace>'Affected if A ServiceAccount exists in a namespace (not kube-system or operator's own namespace) that was created for a namespace-scoped MonitorStack
-
Verify ClusterRoleBindings for operator ServiceAccountsRun 'kubectl get clusterrolebindings -o wide' and look for bindings that reference the operator-created ServiceAccounts, then confirm the ClusterRole permissions with 'kubectl get clusterrole <role-name> -o yaml'Affected if A ClusterRoleBinding associates a namespace-scoped ServiceAccount with a ClusterRole that grants cluster-wide privileges
A tenant with namespace-level permissions is affected if they can create a MonitorStack in their namespace, which causes the operator to create a ServiceAccount that can then be impersonated to gain cluster-wide access through an associated ClusterRoleBinding.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict the Operator's ability to create ClusterRole resources for namespace-scoped MonitorStack deployments, or implement RBAC policies that prevent namespace-scoped users from leveraging the Operator-created ServiceAccount for cluster-level access.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2843 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2843 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data