{"answers":{"affected":"3 open source packages ship an affected version, including github.com/rhobs/observability-operator.","exploited":"There is no known exploitation of CVE-2025-2843 in the wild and no public exploit code.","fix":"Upgrade github.com/rhobs/observability-operator to 1.3.0 or later.","what":"CVE-2025-2843 is a high-severity vulnerability in Red Hat Cluster Observability Operator 1.3.1, published on 12 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-2843 and fix it if it is affected.\n\nWhat it is: CVE-2025-2843 is a high-severity vulnerability in Red Hat Cluster Observability Operator 1.3.1, published on 12 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-2843 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/rhobs/observability-operator (Go): affected all versions; fixed in 1.3.0\n- github.com/rhobs/observability-operator (Go): affected all versions; fixed in 1.3.0\n- github.com/rhobs/observability-operator (Go): affected all versions; fixed in 1.3.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-2843/ (Markdown: https://insights.sbomify.com/CVE-2025-2843/index.md)","id":"CVE-2025-2843","markdown":"https://insights.sbomify.com/CVE-2025-2843/index.md","name":"CVE-2025-2843","record":{"aliases":["GHSA-mj6p-p843-x5wc","GO-2025-4125"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes observability operator","requires_auth":"low_privilege","summary":"A tenant with namespace-level access can escalate to cluster-level privileges by impersonating a ServiceAccount created by the Observability Operator.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Observability-operator: observability operator privilege escalation","id":"CVE-2025-2843","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-2845"},"packages":[{"ecosystem":"Go","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"github.com/rhobs/observability-operator","purl":null,"source":"GHSA-mj6p-p843-x5wc"},{"ecosystem":"Go","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"github.com/rhobs/observability-operator","purl":"pkg:golang/github.com/rhobs/observability-operator","source":"GHSA-mj6p-p843-x5wc"},{"ecosystem":"Go","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"github.com/rhobs/observability-operator","purl":"pkg:golang/github.com/rhobs/observability-operator","source":"GO-2025-4125"}],"prev":{"headline":"Tempo-operator: tempo operator token exposition lead to read sensitive data","id":"CVE-2025-2842"},"products":["Cluster Observability Operator 1.3.1","observability-operator"],"published":"2025-11-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["Red Hat","rhobs"]},"summary":"A tenant with namespace-level access can escalate to cluster-level privileges by impersonating a ServiceAccount created by the Observability Operator.","url":"https://insights.sbomify.com/CVE-2025-2843/"}